Not sure why this didn't occur to me until just now. Unless I'm missing the obvious, each time I restart, the temperature history data is reset. All the readings since the last time HDS was run are lost. Is that true?
Data for Alerts and Logs is kept, but not temperature. I just had a machine hang, had to power off. Drive is hot on reboot, Wish I could go back and see when the temperature reached this setting. Not possible with HDS.
Please tell me what I'm missing or please add this feature.
Temperature data should be logged to disk at user defined intervals for a maximum window of time also user specified.
Obvious flaw in HDS - temperature history
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Obvious flaw in HDS - temperature history
Yes, this is completely normal and expected. There is no "flaw" here.
On Temperature page the "Current" tab - as its name suggests - shows the current, actual temperature value - and some previous values to check how the temperature changes - but only since the startup of the software.
When you completely close and restart, yes, the measurements starts with fresh values, exactly to prevent confusion. For example if you'd power OFF the system at the evening, then powering ON next morning, the previous values may look weird or even cause confusion.
This is exactly why the daily average / maximum / minimum values kept - but the current values not designed to show (big) history or logged values, just the most recent readings in the current session.
Thanks for your suggestion anyway about a possible change, it was not yet planned until now.
On Temperature page the "Current" tab - as its name suggests - shows the current, actual temperature value - and some previous values to check how the temperature changes - but only since the startup of the software.
When you completely close and restart, yes, the measurements starts with fresh values, exactly to prevent confusion. For example if you'd power OFF the system at the evening, then powering ON next morning, the previous values may look weird or even cause confusion.
This is exactly why the daily average / maximum / minimum values kept - but the current values not designed to show (big) history or logged values, just the most recent readings in the current session.
Thanks for your suggestion anyway about a possible change, it was not yet planned until now.
Re: Obvious 'missing feature' in HDS - temperature history
ok, thanks for confirming I'm not over looking something - so many options to begin with.
But yes, also thanks for considering this. Asides from laptops, most of my systems run 24/7. I don't often look at the temperature graphs unless something needs attention.
After a system hang yesterday, upon rebooting, one of my SSD's was red. I wanted to know how long it had been at that temperature. This was not possible since history was lost when I had to power off the system to reset it. Since it was hung, even if I had noticed the temperature then, I could not have looked at the history since the system was unresponsive.
Temperature data is just as important as the Log and Alerts data. Please considering logging that soon. You've already done the hard part - gather the data - now just save it
But yes, also thanks for considering this. Asides from laptops, most of my systems run 24/7. I don't often look at the temperature graphs unless something needs attention.
After a system hang yesterday, upon rebooting, one of my SSD's was red. I wanted to know how long it had been at that temperature. This was not possible since history was lost when I had to power off the system to reset it. Since it was hung, even if I had noticed the temperature then, I could not have looked at the history since the system was unresponsive.
Temperature data is just as important as the Log and Alerts data. Please considering logging that soon. You've already done the hard part - gather the data - now just save it