Summary
With the new Alert Suppression feature, users can now prevent alerts from creating incidents or triggering notifications for known production issues. Alerts can be suppressed in the following ways:
Manually suppress individual alerts from the alert details page or suppress multiple alerts in bulk from the alerts list.
Automatically suppress alerts via workflows that meet the conditions defined in the workflow’s condition nodes.
Suppress alerts and prevent them from creating incidents or triggering notifications when any asset/service is under maintenance. Users can enable alert suppression when creating or updating a maintenance window. They must ensure the respective asset/service is attached to the associated change.
Steps to suppress the alerts via the maintenance window:
Create a maintenance window with alert suppression enabled.
Associate a change with this maintenance window.
Associate the asset/service under maintenance to this change.
Alerts generated during the maintenance window associated with this asset/change will be suppressed automatically.
An alert can be associated with an asset/service in the following ways:
a) The alert is generated from the monitoring tool mapped to the service (applicable for both single-service and multiple-service mappings).
b) The alert has the same resource name as the asset/service. If there are duplicate asset names, none of the assets will be associated with the alert.
c) Services associated only with impact calculation will not be considered for suppression. Only the primary asset/service will be considered for suppression.
Notes:
- Alerts will be suppressed for the whole duration of the maintenance window.
- The maintenance window and the asset causing the alert to be suppressed are present in the alert activities.
- When an alert is associated with any asset via the resource name the user can navigate to that asset details page by clicking on the resource name from the alert details page.
