Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > 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,215 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