Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 9c70291

Browse files
committed
Add step for recurrence
1 parent 3973e4b commit 9c70291

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

alerts-detectors-notifications/mute-notifications.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,10 +94,11 @@ Configure your muting rule:
9494
:width: 90%
9595
:alt: Configure a muting rule
9696

97-
#. Use :guilabel:`Add property` to add (or modify) one or more properties for which you want to mute notifications. If using groups, you can also type :strong:`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.
98-
#. Specify the :guilabel:`Schedule` during which notifications are muted (muting period) using the predefined periods or by creating a custom period. You can also mute indefinitely.
97+
#. Use :guilabel:`Add property` to add or modify one or more properties for which you want to mute notifications. If using groups, you can also type :strong:`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.
9998
#. Include a :guilabel:`Reason` for the muting rule. The text you enter in this field is displayed when you hover over a rule in the :guilabel:`Muting Rules` tab, and can help others understand why alerts are being muted.
100-
#. 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.
99+
#. Specify the :guilabel:`Schedule` during which notifications are muted (muting period) using the predefined periods or by creating a custom period. You can also mute indefinitely.
100+
#. (Optional) If the rule follows a schedule, you can set a recurrence period for the muting rule. A scheduled muting rule can repeat on a daily or weekly basis. Select :menuselection:`Custom` to set a custom recurrence period.
101+
#. 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 Splunk On-Call, OpsGenie, and PagerDuty.
101102
#. Select whether you want to receive notifications for alerts that are still active when the muting period ends.
102103
#. Select :guilabel:`Next` to view a summary of the muting conditions. If you want to turn on the muting rule, select :guilabel:`Save`. It can take up to a minute before a new muting rule goes into effect.
103104

0 commit comments

Comments
 (0)