Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Alerts do not reset

Alerts do not reset

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

Views: 5,020 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