A mute timing is a recurring interval of time when no new notifications for a policy are generated or sent. Use them to prevent alerts from firing a specific and reoccurring period, for example, a regular maintenance period.
Similar to silences, mute timings do not prevent alert rules from being evaluated, nor do they stop alert instances from being shown in the user interface. They only prevent notifications from being created.
Mute timings vs silences
The following table highlights the key differences between mute timings and silences.
|Uses time interval definitions that can reoccur||Has a fixed start and end time|
|Is created and then added to notification policies||Uses labels to match against an alert to determine whether to silence or not|
Create a mute timing
- In the Grafana menu, click the Alerting (bell) icon to open the Alerting page listing existing alerts.
- Click Notification policies.
- From the Alertmanager dropdown, select an external Alertmanager. By default, the Grafana Alertmanager is selected.
- At the bottom of the page there will be a section titled Mute timings. Click the Add mute timing button.
- You will be redirected to a form to create a time interval to match against for your mute timing.
- Click Submit to create the mute timing.
Add mute timing to a notification policy
- Identify the notification policy you would like to add the mute timing to and click the Edit button for that policy.
- From the Mute Timings dropdown select the mute timings you would like to add to the route.
- Click the Save policy button to save.
A time interval is a definition for a moment in time. If an alert fires during this interval it will be suppressed. All fields are lists, and at least one list element must be satisfied to match the field. Fields also support ranges using
monday:thursday). The fields available for a time interval are: mute timing can contain multiple time intervals. A time interval is a specific duration when alerts are suppressed from firing. The duration typically consists of a specific time range along with days of a week, month, or year.
All properties for the time interval are lists, and at least one list element must be satisfied to match the field. The fields support ranges using `:` (ex: `monday:thursday`). If you leave a field blank, it will match with any moment of time.
Supported time interval options are:
- Time range: The time inclusive of the starting time and exclusive of the end time in UTC. - Days of the week: The day or range of days of the week. Example:
monday:thursday. - Days of the month: The date 1-31 of a month. Negative values can also be used to represent days that begin at the end of the month. For example:
-1for the last day of the month. - Months: The months of the year in either numerical or the full calendar month. For example:
1, may:august. - Years: The year or years for the interval. For example:
If a field is left blank, any moment of time will match the field. For an instant of time to match a complete time interval, all fields must match. A mute timing can contain multiple time intervals.
If you want to specify an exact duration, specify all the options. For example, if you wanted to create a time interval for the first Monday of the month, for March, June, September, and December, between the hours of 12:00 and 24:00 UTC your time interval specification would be:
- Time range:
- Start time:
- End time:
- Start time:
- Days of the week:
3, 6, 9, 12
- Days of the month:
Related Grafana Cloud resources
How to set up and visualize synthetic monitoring at scale with Grafana Cloud
Learn how to use Kubernetes, Grafana Loki, and Grafana Cloud’s synthetic monitoring feature to set up your infrastructure's checks in this GrafanaCONline session.
Using Grafana Cloud to drive manufacturing plant efficiency
This GrafanaCONline session tells how Grafana helps a 75-year-old manufacturing company with product quality and equipment maintenance.