Mute Notifications
During a major outage, the same problem often triggers alert after alert while your team is already working the fix. Muting a team stops the repeat paging without stopping the record.
What Muting Does
Section titled “What Muting Does”When a team is muted:
- New and existing alerts for that team stop sending notifications and escalations.
- Alerts still arrive and are still recorded — nothing is lost.
- You are assigned as the alert owner for new alerts raised while the mute is active.
- Suppressed notifications are written to each alert’s timeline as
muteEmail,muteSms, ormutePhoneentries, so you can see afterwards exactly what would have been sent.
Mute Duration
Section titled “Mute Duration”A mute is set for a fixed length of time and expires on its own.
- Minimum: 5 minutes
- Maximum: 24 hours
The mute automatically lifts when the time expires — there is no way to leave a team muted indefinitely by accident. You can also unmute manually at any time before expiry.
Mute a Team
Section titled “Mute a Team”- Navigate to the team you want to mute
- Open the mute control
- Set the mute length in hours and minutes (between 5 minutes and 24 hours)
- Confirm
The remaining mute time is displayed as a countdown while the mute is active.
Unmute a Team
Section titled “Unmute a Team”You can end a mute early at any time. Once unmuted, notifications and escalations resume immediately for both new and existing alerts.
Who Muted, and When
Section titled “Who Muted, and When”Every mute and unmute is recorded:
- The team record stores which user set the mute.
- The action is written to your account’s audit log as
team-mute-addorteam-mute-remove.
This means “why didn’t we get paged?” always has a traceable answer. See Audit Logs.
What’s Next?
Section titled “What’s Next?”- Alert Lifecycle — how the timeline records suppressed notifications
- Audit Logs — the full record of who changed what
- Setup On-Call Schedules — escalation policies