Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > Network Performance Monitor Getting Started Guide > Reduce alerting noise > Use duration in a SolarWinds NPM alert trigger

Use duration in a SolarWinds NPM alert trigger

Table of contents
No headers
Created by Melanie Boyd, last modified by Chris.Moyer_ret on Oct 04, 2016

Views: 860 Votes: 0 Revisions: 7

Using durations for alerts is a great way to reduce the total number of alerts you receive. There are times when you want an alert to trigger as soon as the condition is detected. Other times, you may only want the alert to trigger when a condition exists for more than a certain amount of time.

For example, the WAN link out of your corporate headquarters might occasionally spike over 80% utilization. However, you only want to be alerted if the link is more than 80% for longer than 10 minutes. Set conditions to receive an alert when the utilization on the WAN link is over 80% for 10 minutes, and you will only receive an alert when there is a sustained spike.

The following example illustrates an alert that includes duration. Ensure that you select the Condition must exist check box and enter a duration.

File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/030/Duration.png

Last modified

Tags

Classifications

Public