Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > Network Performance Monitor Getting Started Guide > Reduce alerting noise > Alerts with multi-element triggers in SolarWinds NPM

Alerts with multi-element triggers in SolarWinds NPM

Table of contents
Created by Chris.Moyer_ret, last modified by Chris.Moyer_ret on Oct 04, 2016

Views: 909 Votes: 0 Revisions: 8

You can use complex conditions to trigger alerts when objects meet separate trigger conditions at the same time. For example, if you have two applications on two separate servers, you can still manage if you lose one application. However, if you lose both applications, you need the system to send a critical alert.

Complex conditions should be used with caution. SolarWinds recommends testing each trigger condition individually before combining them.

On the Trigger Conditions panel, expand Advanced options, and select Enable complex conditions.

File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/020/Enable_Complex_Conditions.png

With a standard alert, you can create an alert for each of the two applications. With a complex condition, you can create a single alert where the application would have to fail on both Server A and Server B in order to generate an alert.

In this example, the primary trigger condition is written for Server A.

File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/020/Multi_Element_1.png

Click Add Section and write a trigger condition for Server B.

File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/020/Multi_Element_2.png

In this example, both conditions must resolve to TRUE in order for the alert to fire, but do not have to relate to each. The condition blocks are evaluated at the same time. If they are all TRUE based on the conditions, the alert triggers. You can add additional conditions to configure granular and complex alerts.

Using condition blocks is a great way to reduce alerts. Instead of receiving an alert for each element, you can receive a single alert.

Use instance names

In the example above, a specific node name is selected in the condition. This works well if the alert has a very limited scope. Another approach is to use instance names in the condition.

File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/020/Alert-Instance-Name.png

Last modified

Tags

Classifications

Public