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 > Archive > 2017October26 - CleanUp > Alert notifications in Ignite

Alert notifications in Ignite

Created by Interspire Import, last modified by Gerald.Prado on Oct 26, 2017

Views: 1,283 Votes: 0 Revisions: 14

Overview

Ignite Alerts have the ability to notify prescribed recipients via email and SNMP traps. There are several options available within Ignite to specify when notifications are sent. These options are termed Notification Triggers. Each option is based upon the status of the alert after it is evaluated. The possible statuses are NORMAL, INFO, LOW, MEDIUM, and HIGH and are based upon the thresholds defined when the alert was created. There is also a status of BROKEN that is set when the alert fails due to an error during execution.

Environment

  • Ignite 4.3 up to Ignite 8.3.407

Details

Notification triggers

The following are the notification triggers currently supported in Ignite.

STATUS_NOT_VISITED

Sends notifications if the alert returns a status that is not NORMAL and is a status that has not been returned since the alert was last NORMAL. This is the default notification trigger.

STATUS_NOT_NORMAL

Sends notifications if the alert returns a status that is not NORMAL regardless of the alert's previous status

STATUS_CHANGED

Sends notifications if the alert returns a status that is not NORMAL and is different from the previous execution

The default notication trigger for all alerts is STATUS_NOT_VISITED.

Change notification triggers

The default notification trigger for all alerts can be changed from the Ignite Management Options page accessed from the Options link on the main page. Select the Advanced Options link and edit the Repository Option named ALERT_NOTIFICATION_TRIGGER. All alerts will inherit this default notification trigger unless the alert's notification trigger has been overridden as described below.

The Ignite web interface currently does not provide the ability to set notification triggers on a specific alert. in versions prior to DPA 9.0 To change an alert's notification trigger, run the following queries in the Database Query Tool found on the Ignite Management Options page:

SELECT ID,ALERTNAME FROM CON_ALERT

 

Note: Record the ID for the alert to be changed and use it in the next query

UPDATE CON_ALERT SET NOTIFYWHEN='<notification_trigger>' WHERE ID=

 

Note: <notification_trigger> is replaced with the appopriate trigger name:

 

(STATUS_NOT_VISITED, STATUS_NOT_NORMAL, or STATUS_CHANGED)

 

and <alertid> is the ID found in the first query.

 

Ignite caches alert definitions, so after changing the notification trigger, you must refresh the alert cache. To do this from the Ignite GUI, click on Options at the top and then on Refresh Ignite Alert Cache.

Notification trigger for broken alerts

If an error occurs during the execution of an alert, the alert status is set to BROKEN. Notifications are sent if the alert did not have a status of BROKEN from its previous execution (assuming recipients were prescribed for the BROKEN status).

 

 

Last modified

Tags

Classifications

Public