Grafana Silences and Mute Timings

Alerts that fire during planned work cause panic and wasted effort. A team that upgrades a database at midnight does not want fifty messages telling them the database is down. Silences and mute timings stop notifications for the right alerts at the right moments, while the rules keep running in the background.

The Do Not Disturb Analogy

Your phone offers two ways to quiet things down. You can switch on Do Not Disturb for the next two hours, or you can schedule a quiet period every night from 10 PM to 7 AM. Grafana offers the same pair. A silence is the one-time switch, and a mute timing is the repeating schedule.

Silence        |=== one-time window ===|
Mute timing    |==|    |==|    |==|    |==|   (repeats)
               Sat      Sat      Sat      Sat

What Both Tools Do

Both tools suppress notifications. The alert rules continue to evaluate, and alert states continue to change. You still see the alert in the Alerting page and in the state history. Only the message to the contact point stays quiet.

Rule fires --> Notification policy --> Silenced? --> Muted? --> Contact point
                                          yes: stop     yes: stop
                                          no: continue  no: send

Silences

A silence blocks notifications for alerts that match certain labels, during a set period. Use a silence for one-time maintenance or for an incident that already has an owner.

Create a Silence

Open Alerting and choose Silences.
Click Add silence.
Set the start time and the duration.
Add one or more matchers.
Write a comment that explains why.
Save the silence.

A shortcut exists too. Open any firing alert in the list and click Silence, and Grafana fills the matchers for you.

Matchers

A matcher compares a label with a value.

Operator	Meaning	Sample
=	Equals	team = payments
!=	Does not equal	severity != critical
=~	Matches a pattern	instance =~ web-.*
!~	Does not match a pattern	instance !~ test-.*

A silence with several matchers applies only to alerts that satisfy all of them. The matchers team = payments and instance =~ web-.* silence payment alerts from web servers and nothing else.

Silence States

Pending silences wait for their start time.
Active silences block notifications now.
Expired silences have finished and stay in the list for reference.

Expire an active silence early once the work ends. Alerts flow again right away.

Mute Timings

A mute timing blocks notifications during recurring time windows. Attach it to a branch of the notification policy tree. Alerts that route through that branch go quiet while the timing is active.

Create a Mute Timing

Open Alerting, choose Notification policies, and select the Mute Timings tab. Click Add mute timing and describe the schedule.

Field	Sample Value	Meaning
Time range	22:00 to 06:00	Overnight hours
Days of the week	saturday, sunday	Weekend days
Days of the month	1, 15	Specific dates
Months	december	One month of the year
Location	Asia/Kolkata	The time zone for the schedule

Always set the location. Without it, the schedule runs in UTC and the quiet hours land at the wrong time.

Attach the Timing to a Policy

Edit a notification policy and pick the mute timing in the Mute timings field. Every alert that matches the policy stays quiet during the scheduled window.

Default policy
 |
 +-- team = payments   -> Slack #payments
 |
 +-- severity = low    -> Email digest
       mute timing: "Nights and Weekends"

Low severity alerts wait for office hours. Critical alerts still reach people at any hour, because the critical branch carries no mute timing.

Silence or Mute Timing

Question	Silence	Mute Timing
Repeats on a schedule	No	Yes
Targets alerts by	Matchers on labels	Position in the policy tree
Best for	Planned work and active incidents	Nights, weekends, holidays
Needs a comment	Yes, by good habit	No

Good Habits

Choose the narrowest matchers that cover the work. A broad silence hides real trouble.
Set an end time on every silence.
Write a comment with the reason and your name.
Keep critical alerts outside nightly mute timings.
Review the Silences list weekly and remove forgotten entries.

Previous lesson

Back to course

Next lesson