I did the update to 2026.1.1 and it was definitely an interesting update.
This is one of the issues that crept up on about 40 nodes - Windows Servers and various Cisco equipment.
https://solarwindscore.my.site.com/SuccessCenter/s/article/Node-status-Critical-with-polling-is-failing-message-after-upgrade-to-SolarWinds-Platform-2026-1?language=en_US
Maybe hold off until the next update. It was definitely more fun that I had planned.
This will definitely catch out environments that have broad “Node Status is Critical” type alerts. (some people really do set those up) 😕
It highlights the importance of polling-health alerts and hygiene across the platform, not just for nodes, but also volumes, interfaces and components.
There is probably a wider conversation around context for things like NCM failures as well, but node polling health alone is a good place to start I guess..
I think the change was good. Previously the issue was just hidden. Now it's visible.
I always have a report available, that showed all nodes with polling issues, keeping a healthy monitoring environment. Now, it will be very clear where there are polling issues that need to be dealt with.
I liked this change, because in the past when someone did something mad like use a personal account for customer monitoring they would ultimately change their password and monitoring would silently fail but the node was still Up because ping. Occasionally I'd be looking through the logs for a different polling issue and find a load of 'invalid credentials' WMI failures because of this, so at least now we'd be able to see what was going on.
This scenario will definitely expose environments that rely on broad “Node Status is Critical” type alerts, which unfortunately some deployments still use. 😕
It highlights the importance of maintaining proper polling health visibility and alert hygiene across the SolarWinds platform — not only for nodes, but also for interfaces, volumes, applications, and components.
There is likely a broader discussion to be had around contextual alerting for areas such as NCM job failures and configuration-related events as well. However, improving node polling health monitoring and alert logic is certainly one of the best places to start for reducing false positives and improving operational visibility.
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices.pollerCisco ASR Devices
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…
Active SSL Tunnels-ASA.UnDPThis poller *should* display the number of Active SSL VPN (Anyconnect) Tunnels currently connected to your box. However, I tried it with my 5520 running 8.0.4 and for some reason I get a OID Not Supported. Here's my post in the forum: *EDIT* This is confirmed working with at least Interm release…
