Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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: 87 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
23:12, 22 Jun 2016

Tags

Classifications

Public