When viewing a host in SolarWinds Observability that has a Bad/Critical health status, there is currently no clear indication on the Node Health view explaining exactly what has caused the node to enter that state.
The red health status tells you that something is wrong, but it does not provide an obvious, actionable explanation of the underlying issue. To determine the cause, you have to manually investigate areas such as Performance or Node Metrics until you find the metric or condition responsible.
The Node Health tab should clearly show the reason or reasons why the node is currently in a Bad/Critical state.
For example, it should display something along the lines of:
- Critical: CPU utilisation has exceeded the configured threshold
- Critical: Memory utilisation has exceeded the configured threshold
- Critical: Disk space on C: is below the configured threshold
- Critical: Packet loss exceeds the configured threshold
More importantly, the health issue should be clickable, taking the user directly to the relevant metric, alert, chart or area that caused the health status.
Ideally, the Node Health tab should provide:
- A clear explanation of exactly why the node is Bad/Critical.
- The metric or condition responsible for the health state.
- The current value and relevant threshold, where applicable.
- A clickable link to the affected metric or relevant monitoring view.
- Multiple contributing issues listed separately if more than one condition is affecting the node's health.
The purpose of the Node Health view should be to answer the immediate question: "Why is this node unhealthy?"
Administrators should not have to manually search through performance charts and node metrics to determine why SolarWinds Observability has marked a node as Bad/Critical.
Making the health status clear and actionable would significantly reduce the time required to identify and troubleshoot issues.