Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

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

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
20:03, 11 Apr 2017

Tags

Classifications

Public