Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Add Escalation Level to alert in SolarWinds NPM

Add Escalation Level to alert in SolarWinds NPM

Updated January 9, 2019


This article describes how to escalate alert priority levels in SolarWinds NPM.


  • NPM 12 .2 and later


Escalation levels in Orion Platform products refer to user-defined time intervals between when an alert is activated and when a user acknowledges that alert. You can configure the alert to perform different actions per escalation level.

Level Description
Escalation Level 1 Contains all initial actions that you want to occur when the trigger conditions are met and the alert activates.
Escalation Levels 2 and above Include all actions you want to occur if no one acknowledged the alert during the previous escalation levels.


For example, if an alert for a critical server activates and all of the recipient or first-level responders are out for training and do not acknowledge the alert, then the actions fire in the second escalation level. These actions may include emailing managers or other backup staff.

How to escalate alerts:

  1. In an existing alert, click Trigger Actions.
  2. Below the action, click Add Escalation Level.
  3. Select how long to wait for the previous escalation level before performing the actions in the new escalation level.
  4. Enter actions to be completed this escalation level.
  5. After you have completed added escalation levels and actions, click Next to configure the reset actions, or click Summary to review your changes and save them.
  6. Click Copy Actions to Reset Actions Tab to copy all of the actions as Reset Actions and record that the issue has been acknowledged or resolved.


Last modified