[QUESTION]

[wfahnestock]

Which component is your question about?

Lite

Performance Monitor Version

2.9.0

Is your question about how it works, or the results?

How the tool works

What's your question?

Is there any way to "silence" "active" alerts? Ran into a deadlock situation on one of my monitored servers. Resolved the issue, however "x deadlocks detected in last hour" kept sending the alert as "Deadlocks detected" (i.e: right now) via my Teams webhook, up to an hour after the issue was resolved. I'd really like a way to have more control over what and when alerts are being sent via email/webhook.

Additional Context

No response

[erikdarlingdata]

Hi @wfahnestock — good news, there's a built-in way to do this in 2.9.0.

Workaround: temporary mute rule

In Lite, open Settings → Manage Mute Rules… → Add, then set:

• Metric: Deadlocks Detected
• Server: the affected server name
• Expires: ~1 hour from now (long enough for the rolling 1-hour window to roll past the resolved deadlocks)

This silences both the email and the Teams/Slack webhook for that server+metric until the rule expires (it auto-purges on expiry). Other servers and other alert types keep firing normally.

You can also leave Expires blank for an indefinite mute and toggle the rule off later, or scope it more narrowly (e.g. by database) if that's useful.

The real ergonomic gap

You're right that discovering and configuring a mute rule mid-incident is more friction than it should be. I'll open a follow-up enhancement to add a one-click "snooze this alert for 1 hour" action directly on active alerts (and ideally in the email/webhook payload itself), which would address the underlying complaint here. Linking it back to this issue.

[erikdarlingdata]

Filed #944 to track the one-click snooze enhancement.

[erikdarlingdata]

@wfahnestock — first half of the snooze enhancement is now in dev (#946) and will be in the next nightly build.

What you'll see when an alert fires (CPU, Blocking, Deadlocks, Poison Wait, Long-Running Query, TempDB Space, or Long-Running Job):

• The standard Windows toast is replaced with a small popup that has Snooze 15m / 1h / 4h and Dismiss buttons.
• Clicking a Snooze button creates a temporary mute rule scoped to that server + metric for the chosen duration. The rule auto-purges when it expires.
• While snoozed, all three channels stay quiet for that server+metric — tray popup, email, and Teams/Slack webhook. Other servers and other alert types keep working normally.
• You can still see/manage active rules in Settings → Manage Mute Rules, and toggle them off early if you want.

For your deadlock scenario specifically: when the alert fires, click Snooze 1h and the Teams webhook will stay quiet for the full hour while the rolling-window count drains.

When you've had a chance to install the nightly and try it, please leave a comment here with how it worked — anything awkward, missing, or wrong durations to offer? The follow-up PR (still tracked on #944) will add a discoverability line to the email body and Teams/Slack message itself, so even when the alert lands somewhere other than the desktop you'll know how to silence it.

[erikdarlingdata]

Quick update: the second half of the snooze enhancement (#947) just merged into dev and will also be in the next nightly build alongside #946.

What's new on this side:

• Alert emails (HTML and plain-text) now include a footer line: "To silence this alert: open Performance Monitor Lite → Settings → Manage Mute Rules"
• Teams alert messages get the same hint as a small section at the bottom of the card
• Slack alert messages get it in the context line at the bottom

Test emails / test webhook payloads stay clean — the hint only shows on real alerts.

When you try the nightly, please share any feedback on either half (popup buttons, email/webhook footer text, anything else awkward) right here. Closing #944 since both halves shipped, but keep the conversation on #943 — that's the one you opened.