Mute alert notifications 🔗
Muting is helpful when you need to stop sending alert notifications during situations that are known to trigger alerts, such as maintenance windows or tests. Muting allows you to reduce noise and focus on what really matters.
You can stop sending, or mute, alert notifications based on certain conditions you can specify. You can mute notifications for a specified period of time or indefinitely, although alerts and events are still generated, and appear in Observability Cloud.
To see your existing muting rules or create new ones, go to Alerts, then select the Muting Rules tab.
How muting works 🔗
Alert notifications are muted according to muting rules, which include a schedule that sets the muting period. During the muting period, notifications that match the rule aren’t sent to subscribers. The only exception are clear notifications for alerts that were active before the muting period started.
After the muting period ends, Observability Cloud re-starts sending to subscribers notifications for alerts that are still active, or for alerts triggered within the last 90 days of the muting period. To disable sending alert notifications after the muting period has ended, edit the muting rule configuration.
Muting rules only affect notifications: When a muting rule is active, alerts and events that are muted by the rule are still generated.
Create muting rules 🔗
To create a muting rule, you can either:
Mute specific detectors or alerts 🔗
Creating muting rules from existing detectors or alerts is the fastest way of muting notifications.
To mute a specific detector or alert:
Open the Alerts page, and locate the detector or active alert you want to mute.
Select the more icon (⋯) next to the detector or alert, and select.
To mute a detector while you’re editing it, select from the detector’s action menu (⋯).
Create muting rules based on group-by dimensions 🔗
Muting rules automatically include dimensions specified in Group By, so that you can mute notifications from multiple detectors with a single muting rule.
To create muting rules based on group-by dimensions:
Open Alerts, then select either the Active Alerts or Detectors tab.
Specify the grouping dimensions using the Group By buttons.
Select the more button (⋯) next any grouped item, and select.
Achieve greater precision in your muting rules by using built-in dimensions instead of metadata collected asynchronously, such as AWS tags.
Create muting rules from scratch 🔗
Create or edit muting rules at any time from the Muting Rules tab in Alerts.
To create a new muting rule from scratch:
Open Alerts, then select the Muting Rules tab.
Configure your muting rule 🔗
Configure your muting rule:
Use Add property to add (or modify) one or more properties for which you want to mute notifications. If using groups, you can also type sf_tags to find a list of tags. When you add more than one property, the muting rule interprets the properties using the AND logical operator.
Specify the Schedule during which notifications are muted (muting period) using the predefined periods or by creating a custom period. You can also mute indefinitely.
Include a Reason for the muting rule. The text you enter in this field is displayed when you hover over a rule in the Muting Rules tab, and can help others understand why alerts are being muted.
Select whether you want to clear any existing alerts that match the conditions you have set. If you’re muting certain alerts to address a known problem, you might want to clear existing alerts so you are starting from a clean slate. Clearing these alerts also notifies downstream systems, such as VictorOps, OpsGenie, and PagerDuty.
Select whether you want to receive notifications for alerts that are still active when the muting period ends.
Select Next to view a summary of the muting conditions. If you want to turn on the muting rule, select Save. It can take up to a minute before a new muting rule goes into effect.
Observability Cloud allows a maximum of 9,500 muting rules.
Search and view muting rules 🔗
You can search existing muting rules and view their details at any time, as well as browse muted notifications.
Active and scheduled muting rules 🔗
To find active or scheduled muting rules, use the search field in the Muting Rules tab on the Alerts page.
You can also view information about active and scheduled muting rules from different places on the Alerts page.
On the Muting Rules tab, you can view a list of all active and scheduled muting rules.
On the Detectors and the Active Alerts tabs, running or scheduled muting rules are indicated by red labels next to the muted item.
Muted notifications 🔗
If a notification was muted, an indicator is displayed wherever the event would have sent the notification, such as on the Active Alerts tab or in an event feed.
To see events related to past muting rules, you can use the Events sidebar or the Event overlay. Events are generated when the rule becomes active (notifications stop) and when the rule becomes inactive (notifications resume).
To find muting events in the Events sidebar, search for sf_eventType:alertMuting.
To overlay muting events on a dashboard, search for alertMuting in the Event Overlay search box.
Cancel or delete muting rules 🔗
Canceling an active muting rule and resuming notifications for an alert or detector are the same thing. A canceled muting rules is deleted from Observability Cloud before it expires. Scheduled muting rules that are not yet active can also be deleted before they start.
To cancel an active muting rule or delete a scheduled muting rule from Alerts:
Select the Muting Rules tab, and locate the muting rule you want to cancel or delete.
Select the more icon (⋯) next to the muting rule and selector .
You can also cancel muting rules from a muted alert or detector:
On the Active Alerts or the Detectors tab, select the muted or the notifications muted label.
For a detector, select the muting rule, then select.
For an active alert, select the more icon (⋯), then select.
If there are multiple rules, select the rule for which you want to resume notifications. In each case, you can confirm that you want to resume sending notifications.