Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

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: 1,318 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