Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Incorrect CPU percentage variable data after an alert was triggered

Incorrect CPU percentage variable data after an alert was triggered

Table of contents

Updated April 11, 2017


The CPU percentage alert variable is showing incorrect data. For example, an alert will trigger if the CPU percentage is above 90% or if the usage spikes. The alert variable will populate a value that is below the threshold percentage making it appear that the alert should not have triggered.


Orion NPM 12.x environments


The true percentage value that triggered the alert did not populate in the alert variable, rather, a later polled and inappropriate value was used. This value can be found in the historical data and the cause of this issue is currently being investigated.


Last modified