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 > NPM alert fails due to incorrect reset condition

NPM alert fails due to incorrect reset condition

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,369 Votes: 0 Revisions: 8

Issue:

An NPM alert fails to trigger because the reset condition is misconfigured.

Cause:

The reset condition in this case (see sample screen below) is so set that the node status is always True and stops the alert from triggering.

alert2.gif

alert1.gif

Resolution:

  1. Remove the incorrect reset condition "Node Status is equal to Up"  and change it to "Reset when Trigger Conditions are no longer true".
  2.  Add this condition "Node Status is equal to Up" to the trigger condition tab.

The alert should now trigger properly.

Last modified

Tags

Classifications

Public