From c81b7a0400b29d649e3b97a38e79064863322576 Mon Sep 17 00:00:00 2001 From: "Johnny K." Date: Mon, 12 Jan 2026 12:39:29 -0600 Subject: [PATCH] edit --- .../shared/alerts/mute-timings-vs-silences.md | 20 +------------------ 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/docs/sources/shared/alerts/mute-timings-vs-silences.md b/docs/sources/shared/alerts/mute-timings-vs-silences.md index 0a7e1d8835a..4fb33c8708e 100644 --- a/docs/sources/shared/alerts/mute-timings-vs-silences.md +++ b/docs/sources/shared/alerts/mute-timings-vs-silences.md @@ -14,22 +14,4 @@ The following table highlights the key differences between mute timings and sile | | Mute timing | Silence | | ---------- | ----------------------------------------------------------- | ---------------------------------------------------------------- | | **Setup** | Created and then added to notification policies | Matches alerts using labels to determine whether to silence them | -| **Period** | Uses time interval definitions that can repeat periodically | Has a fixed start and end time | - -**When to use mute timings** - -Use mute timings for predictable, recurring time periods when you don't want to receive notifications: - -- Regular maintenance windows (for example, every Sunday from 2:00 AM to 4:00 AM) -- Non-business hours (for example, nights and weekends) -- Scheduled deployments or known change windows -- Regular testing periods - -**When to use silences** - -Use silences for one-time or ad-hoc suppression of notifications: - -- Active incident response (suppress notifications while investigating) -- Immediate suppression of a specific alert or group of alerts -- One-time maintenance or deployment events -- Temporarily suppress alerts for specific services or components +| **Period** | Uses time interval definitions that can repeat periodically | Has a fixed start and end time | \ No newline at end of file