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) > Alerts do not reset

Alerts do not reset

Created by Erica Gill, last modified by Shane Horgan on Oct 06, 2016

Views: 4,338 Votes: 0 Revisions: 5


This article describes how to address a scenario where alerts may not reset.

For example, specific alerts may not reset despite the trigger condition no longer being true.


  • NPM v11.5
  • NPM v12


This issue occurs when an active alert is modified after it has triggered and the triggered instance of the alert is effectively orphaned.


  1. Confirm if the alert has been modified since the alert triggered.
    Confirm that the triggered instance of the alert is no longer valid.
  2. If both the above are true, clear the triggered instance of the alert which is incorrect by performing the next steps.
  3. Log into the Orion Web Console as Admin user or one which has alert management rights.
  4. Click on Setting in the upper right corner.
  5. Click on Manage Alerts.
  6. Click on Active Alerts.
  7. Select the affected alerts and click on Clear triggered instance of alert.

To avoid this issue, stop the alert before modifying it and clear any triggered instances of the alert which have no been cleared automatically.



Last modified