Skip to content

Commit ed34127

Browse files
committed
Add mute_intervals section to routing-by-time docs
https://claude.ai/code/session_01FGiv1N3QcFMWAPT4e1pu93
1 parent 937861c commit ed34127

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

docs/notification-routing/routing-by-time.rst

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,33 @@ As seen above, a sink can be active during multiple ``intervals``. Each interval
3535

3636
Sinks that don't define an ``activity`` field are always active.
3737

38+
Mute Intervals
39+
--------------
40+
41+
You can also mute a sink during specific date ranges using ``mute_intervals``. Unlike ``activity`` (which defines recurring weekly schedules), ``mute_intervals`` defines exact date ranges with a year — useful for holidays, maintenance windows, or one-off silencing.
42+
43+
.. code-block:: yaml
44+
45+
sinksConfig:
46+
- slack_sink:
47+
name: main_slack_sink
48+
slack_channel: robusta-notifications
49+
api_key: xoxb-your-slack-key
50+
mute_intervals:
51+
- start_date: "2025-12-24 00:00"
52+
end_date: "2025-12-26 23:59"
53+
timezone: CET
54+
- start_date: "2026-01-01 00:00"
55+
end_date: "2026-01-01 23:59"
56+
timezone: US/Eastern
57+
58+
Each interval has:
59+
60+
- ``start_date`` and ``end_date`` in ``YYYY-MM-DD HH:MM`` format.
61+
- An optional ``timezone`` (defaults to ``UTC``). Each interval can use a different timezone.
62+
63+
When any mute interval is active, the sink will not emit notifications. You can combine ``mute_intervals`` with ``activity`` — the sink must be active according to ``activity`` *and* not muted by any interval.
64+
3865
.. details:: Supported Timezones
3966

4067
.. code-block::

0 commit comments

Comments
 (0)