From 67f811b6d8cdb8d0b16ea027ab6e8b48ad4f1d6b Mon Sep 17 00:00:00 2001 From: Johnny Kartheiser <140559259+JohnnyK-Grafana@users.noreply.github.com> Date: Wed, 12 Nov 2025 10:49:50 -0600 Subject: [PATCH] alerting: mute timing clarification (#113129) * alerting: mute timing clarification clarify that mute timing takes precedence over active timing * alerting docs: best practices addition draft content for best practices re: recording rules * wrong branch * alerting: best practices docs best practices addition re: recording rules * smh --- docs/sources/alerting/configure-notifications/mute-timings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/alerting/configure-notifications/mute-timings.md b/docs/sources/alerting/configure-notifications/mute-timings.md index f9cb3bd5086..58636eb1965 100644 --- a/docs/sources/alerting/configure-notifications/mute-timings.md +++ b/docs/sources/alerting/configure-notifications/mute-timings.md @@ -46,7 +46,7 @@ A mute timing is a recurring interval that stops notifications for one or multip Use mute timings to temporarily pause notifications for a specific recurring period, such as a regular maintenance window or weekends. -The active time interval provide the opposite functionality, where alerts handled by a notification policy are suppressed unless the notification happens at a time that matches the time interval. Use active time intervals for periods where you want to reduce alert noise. +The active time interval provide the opposite functionality, where alerts handled by a notification policy are suppressed unless the notification happens at a time that matches the time interval. Use active time intervals for periods where you want to reduce alert noise. Mute timings take precedence over active time intervals when they overlap. {{< admonition type="note" >}} Mute timings and active time intervals are assigned to a [specific Alertmanager](ref:alertmanager-architecture) and only suppress notifications for alerts managed by that Alertmanager.