This commit is contained in:
Johnny K.
2026-01-12 12:36:44 -06:00
parent 8fbf19c8b0
commit dea7b621f8
2 changed files with 19 additions and 1 deletions
@@ -90,7 +90,7 @@ Use mute timings for predictable, recurring time periods when you don't want to
**When to use silences**
Use silences for one-time or ad-hoc suppression of notifications:
Use silences for one-time or as-needed suppression of notifications:
- Active incident response (suppress notifications while investigating)
- Immediate suppression of a specific alert or group of alerts
@@ -63,6 +63,24 @@ The following table highlights the key differences between mute timings and sile
| **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 as-needed 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
[//]: <> ({{< docs/shared lookup="alerts/mute-timings-vs-silences.md" source="grafana" version="<GRAFANA_VERSION>" >}})
## Add time intervals