There are times when the clients' device stops polling for whatever reason. This could be an issue with the device or a change in credentials. Almost all clients I have been involved with are not aware that the polling has stopped.
There is a simple way of noticing this, which is by looking at the timestamp of the CPU polling. If it is more than 35 minutes from the current time, the node is having issue.
Using both the report and alert will make sure you are getting data from all nodes and avoid the embarrassing situation when a server crashes due to high CPU and the boss comments - "I thought that SolarWinds was monitoring this".
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.
Learn more today by joining now.