- Joined
- May 19, 2017
- Messages
- 1,829
Here is an additional suggestion to layer on top of the preceding one: Indicate such events in the reporting menu for CPU usage, temperatures, loads, etc.
Just add a simple dot under the timeline axis of whatever graph you're showing. You could color the dots to denote various types of events like system maintenance (scrubs, SMART tests, etc.) vs. more critical events like IGB0 down!, hard drive blew up!, etc. Or, just add the dots and then offer the information via hover-over. Coloring them based on the traffic light pattern used in the GUI is probably a good start (Green for scheduled events / cron jobs, yellow for unhappiness, red for major failures).
This representation would help visualize the cause of an event. If the UI ever adds hard drive temperature reporting / graphing (if this can be done for the CPU, why not the hard drives too?), users would likely be thankful for knowing that the spike they are seeing in hard drive temperatures was due to a SMART test or a scrub event.
Just add a simple dot under the timeline axis of whatever graph you're showing. You could color the dots to denote various types of events like system maintenance (scrubs, SMART tests, etc.) vs. more critical events like IGB0 down!, hard drive blew up!, etc. Or, just add the dots and then offer the information via hover-over. Coloring them based on the traffic light pattern used in the GUI is probably a good start (Green for scheduled events / cron jobs, yellow for unhappiness, red for major failures).
This representation would help visualize the cause of an event. If the UI ever adds hard drive temperature reporting / graphing (if this can be done for the CPU, why not the hard drives too?), users would likely be thankful for knowing that the spike they are seeing in hard drive temperatures was due to a SMART test or a scrub event.