One area I’d like to see SolarWinds HCO continue to evolve is how monitoring data is turned into operational context.
HCO already collects a huge amount of useful signal across nodes, interfaces, volumes, applications, virtualisation, polling, alerts and availability.
For me, the opportunity is not just about a fresher UI or more out-of-the-box dashboards. It is about helping teams move from raw monitoring data into clearer evidence, state and action.
The way I have been approaching this in SolarWinds builds is by treating the platform as an evidence layer.
A node down alert should not just say a node is down.
It should help show recent availability, packet loss, response time, polling health, last good poll, alert history and whether the node has been unstable recently.
A volume alert should not just say a disk is low.
It should help show consumption rate, previous behaviour, recent change, projected runway, business context and whether this is a recurring pattern.
An application alert should not just say a component is critical.
It should help show whether the application is genuinely unhealthy, whether the signal is stale, whether the polling is reliable, whether the node is also unhealthy, and what evidence supports the current state.
That is where I think HCO still has a lot of strength: not just as a monitoring console, but as a platform for structured operational evidence.
For me, the model is:
Evidence → State → Action
Evidence is the raw signal and supporting context.
State is the interpreted operational condition.
Action is what the engineer, service owner or customer should focus on next.
This is the part I’d like to see HCO push further.
Some areas I think would add real value:
Stronger native evidence panels in alerts and dashboards.
More historical comparison out of the box, such as current 7 days vs previous 7 days, baseline movement, trend direction, instability and recurring patterns.
Better polling hygiene visibility across nodes, interfaces, volumes and components.
Alert content that explains why something matters, what changed, what evidence supports it and what the likely focus area is.
Cleaner service, customer and site posture views driven by monitored state, custom properties, availability, SAM data, alert history and trend evidence.
Dashboard components that are less about showing isolated metrics and more about presenting an operational story.
A stronger distinction between raw signal and interpreted state.
I know a lot of this can already be built with custom SQL, SWQL, reports, custom properties, alert enrichment and dashboard design. I have been building this type of approach myself, and the results can be really powerful.
But I think there is an opportunity for HCO to make this style of evidence-led monitoring more native.
SolarWinds has always been strong at collecting infrastructure and application signals. The next evolution, in my opinion, is helping teams turn those signals into clearer operational stories.
Not just:
“What is red?”
But:
What changed?
What evidence supports it?
Is this a current issue, a recurring issue or a stale signal?
Is this a capacity problem, availability problem, polling problem or application health problem?
What service, site or customer is affected?
What should someone look at first?
That is the direction I would love to see HCO continue moving in.
More evidence.
Clearer state.
Better action.
