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) > Set custom thresholds for devices

Set custom thresholds for devices

Table of contents
Created by Richard Casey, last modified by Gary O'Donovan on Dec 29, 2017

Views: 2,606 Votes: 2 Revisions: 6

Updated June 23, 2016


This article provides steps steps to change default threshold for warning or critical thresholds on specific devices or globally in the Orion Web Console.


NPM versions 11 and 12


Change the value on a per node basis:

1. Select the target node.

2.Go to Node Details > Management Resource > Edit Node. 

At the bottom of the page is the option to change alerting thresholds:

3. Select the target threshold (CPU, Memory, Response time or Packet loss) and click Override Orion General Thresholds.

4. Enter the required values for the Warning and Critical levels and click Submit.


To change the Thresholds Globally then:

1. Go to Settings.

2. Click Orion Thresholds.

3. Adjust the values required to be applied to all nodes and then Submit.




Last modified