Muting Alerts

Muting lets you silence an alert temporarily or indefinitely without marking the underlying issue as resolved. This is useful when you are aware of a problem but cannot fix it immediately, or when an alert is firing for a known condition that does not require action.

What is muting?

When you mute an alert, Sazabi suppresses future notifications for that alert. The alert remains open and visible in your dashboard, but it will not ping your team again if the same issue re-fires.

Muted alerts:

Stay in the open state
Do not trigger delivery channel notifications when the issue recurs
Track how many times the alert would have fired (mute hit count)
Can be unmuted at any time to resume notifications

Mute vs resolve

Choosing between muting and resolving depends on the situation:

Action	Use when...
Mute	You acknowledge the issue but cannot fix it yet (e.g., known bug, scheduled maintenance, external dependency)
Mute	The alert is expected behavior that does not require action
Mute	You want to silence noise during a known incident while you work on a fix
Resolve	The issue has been fixed and is no longer occurring
Resolve	The alert was a false positive that will not recur

Think of muting as "I know about this, stop notifying me" and resolving as "this is done."

Mute hit count

While an alert is muted, Sazabi continues tracking when the underlying issue would have triggered a new notification. The mute hit count shows how many times the alert would have fired since it was muted.

This metric helps you understand:

How frequently an issue is recurring
Whether a muted condition is getting worse
When a temporary issue has stabilized

The mute hit count resets when you unmute the alert.

Unmuting

When you unmute an alert, Sazabi resumes normal notification behavior:

The next occurrence of the issue will trigger delivery channel notifications
The mute hit count resets
The alert remains in the open state

You can unmute from any surface where you can view the alert: the dashboard, Slack, or via API.

Muting from Slack

Alert notifications in Slack include an inline Mute button. Clicking it:

Mutes the alert immediately
Updates the Slack message to show the muted state
Displays who muted the alert and when

To unmute, click the Unmute button that replaces the mute action.

This inline workflow lets your team manage alert noise without leaving Slack or opening the dashboard.

Best practices

Set expectations for muted alerts. When you mute an alert, consider leaving a comment explaining why and when you expect to address it. This helps teammates understand the context when they see a muted alert.

Review muted alerts regularly. Muted alerts can accumulate if not periodically reviewed. Check your muted alerts weekly to ensure you are not ignoring issues that have become more severe.
Use muting for temporary conditions. If you find yourself muting the same alert repeatedly, consider whether the alert definition needs adjustment or whether the underlying system needs attention.
Unmute after deployments. If you muted an alert while working on a fix, remember to unmute it after deploying so you can verify the fix is working.