A customer recently asked if I could give them a clearer view of their SolarWinds pollers.
Not just whether the pollers were up, but whether the polling layer itself looked healthy, balanced, resilient and trustworthy.
The node names and IP addresses have been normalised for sharing, but the underlying dashboard data is live.
So I had a go at turning the polling layer into something a bit easier to read.
Pollers do not all carry the same shape of workload, and HA adds another layer to the story. I did not want the dashboard to just throw raw numbers on screen and call it visibility. The useful bit is comparing the right signals in the right context: engine load, collection pressure, polling behaviour, HA state, coverage and anything that suggests the platform is starting to drift.
The idea is simple enough:
- show the pollers
- show where engine load and collection pressure are building
- show whether polling looks balanced
- show HA/resilience state
- show any obvious coverage or load concerns
- make it useful at a glance, not just another table of numbers
SolarWinds already holds a lot of this evidence. The interesting bit is how you shape it.
This started as a simple customer request, but it is turning into a useful little view of the polling layer: part health check, part resilience view, part coverage map, part “where should I look first?” screen.
P.S. If you want to see the wider set of dashboards, ideas and SolarWinds experiments, I’m grouping them all under Observability Solutions.
one for @vinay.by and @naveensingh43 ✌️
