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 > Alerts for volume utilization are not triggered when they appear to have reached their threshold value

Alerts for volume utilization are not triggered when they appear to have reached their threshold value

Last Updated: March 7, 2018

Overview

In some cases, the Volume Utilization value that NPM displays in the Orion Web Console appears to be at the threshold for an alert, and yet the alert is not triggered. 

Environment

  • NPM 12 and later

Cause

This happens because NPM rounds the volume utilization value up or down to display whole numbers in the Orion Web Console. For example, if the volume utilization value is 59.85%, it is displayed as 60% in the Volume Details page of the Orion Web Console. A volume utilization alert with a threshold of 60 is not triggered because the actual value is less than 60.

Resolution

This behavior is by design. However, to avoid the appearance of alerts failing to be triggered, you can adjust the threshold value to less than .5% of your target trigger value. For example, change the trigger condition to Volume Percent Available is greater than or equal to 59.5%.

 

 

Last modified

Tags

Classifications

Public