Define when a triggered alert shouldn’t execute alert actions
This topic applies only to the following products:
SolarWinds Observability Self-Hosted
DPAIM — IPAM — LA — NAM — NCM — NPM — NTA — SAM — SCM — SRM — UDT — VMAN — VNQM — WPM
If you want an alert to only trigger in specific situations, you can define when the configured alert actions should be suppressed.
Suppression conditions limit the alert scope by specifying situations when alert actions should not be executed.
Before you define a suppression
Take into account the following considerations:
-
Suppression is not supported for global alerts that include conditions such as "N or more objects meet the condition".
-
By default, the suppression condition is periodically evaluated every 1 minute. The Evaluation Frequency of Alert setting covers both trigger and suppression conditions.
-
Suppression prevents all actions from firing, including repeated trigger actions, escalated trigger actions, and reset actions.
-
When you exit suppression while the trigger condition is still valid, the alert triggers immediately the trigger (or reset) action.
-
On All Active Alerts, you can filter out suppressed Alerts. Click More > Hide suppressed alerts.
-
To display suppressed alerts in reports, use the "suppressed" property.
-
Suppression-enabled alerts are supported by the product’s API. They can be exported and imported.
Configure suppression in the Add/Edit alert wizard
-
On Suppression Condition, select Define a suppression condition.
-
Click Add Condition and select how to define it:
-
Create a new condition - define when the alert shouldn’t trigger.
The options for defining suppression conditions are fewer than for defining trigger conditions to prevent misconfigurations. You cannot change the scope of the alert, use custom SQL queries, use advanced options or use event-based conditions. See Create your trigger condition.
The suppression condition must use the same "I want to alert on" entity, even though you define properties of different entities. See the example.
-
Copy condition from trigger - copy the trigger condition and modify it to define exceptions from the rule.
-
Import condition from XML file... import a condition as a XML file.
-
-
Review the suppression message and adjust it if appropriate. The suppression message is displayed both in the All Active Alerts list and on the active alert details views.
-
Complete the definition.
If you have successfully created a suppression condition or decided not to use suppression for this alert, you can move to the next step in the alert wizard.
Click Next to define what event occurs to reset the alert.
Example suppression condition: Alert on loopback interfaces only if not on MyPC nodes
To configure an alert to trigger its actions for each loopback interface except for those that are on Nodes that have "MyPC" in names:
Trigger Condition
Alert on interface where caption equals "loopback".
Suppression Condition:
Alert on interface where node name contains "MyPC".
