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

Commit 6f55391

Browse files
committed
Merge branches 'theletterf-o11ydocs-5711-recurring-muting-rule' and 'theletterf-o11ydocs-5711-recurring-muting-rule' of github.com:splunk/private-o11y-docs into theletterf-o11ydocs-5711-recurring-muting-rule
2 parents 7e0e4cf + 54ebc9c commit 6f55391

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

alerts-detectors-notifications/mute-notifications.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,16 +88,18 @@ To create a new muting rule from scratch:
8888
Configure your muting rule
8989
=============================================================================
9090

91-
Configure your muting rule:
91+
The following screenshot shows the muting rule dialog box:
9292

9393
.. image:: /_images/alerts-detectors-notifications/muting-notifications/mutingrule-modal2.png
9494
:width: 90%
9595
:alt: Configure a muting rule
9696

97+
To create a new muting rule, follow these steps:
98+
9799
#. 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.
98100
#. 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.
99101
#. Specify the :guilabel:`Schedule` during which notifications should be 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 :guilabel:`Schedule`, you can set a recurrence period for the muting rule. When scheduling a muting rule, the rule repeats after a set number of days, starting with the start time of the original rule. The daily and weekly options set that number to ``1`` and ``7`` respectively. The :menuselection:`Custom` option lets you set the number of days or set a number of weeks.
102+
#. (Optional) If the rule follows a schedule, you can set a :guilabel:`Recurrence` period for the muting rule. When scheduling a muting rule, the rule repeats after a set number of days, starting with the start time of the original rule. The daily and weekly options set that number to ``1`` and ``7`` respectively. The :menuselection:`Custom` option lets you set the number of days or set a number of weeks.
101103
#. 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.
102104
#. Select whether you want to receive notifications for alerts that are still active when the muting period ends.
103105
#. 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.

0 commit comments

Comments
 (0)