Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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

Overview

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.

Environment

Orion NPM 12.x environments

Detail

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

Tags

Classifications

Public