Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
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
20:03, 11 Apr 2017