Review stale or dangerous error suppressions

Find suppressions that are hiding high-volume, high-impact, or recently regressed errors before noise rules mask real incidents.

Published

difficulty beginner · time to value 2 minutes
#errors #suppressions #oncall #governance #ops #sentry-alternative

Start from this 

Review current suppressions and tell me which ones are stale, too broad, or hiding errors that recently affected real users.

Why this matters

Suppressions start as a mercy and become blind spots. A broad rule that was safe last month can hide a revenue-impacting regression after a deploy.

What you get

  • Suppression rules with recent matching cases
  • Rules that match too many fingerprints
  • Suppressed cases with user or revenue impact
  • Recommendations to narrow, expire, or remove rules

Walk through it

You

Are any suppressions hiding real problems?

Agent

I’ll list suppression rules and compare them with current open and ignored cases.

GET /v1/projects/:project_id/suppressions { project_id: "default" }
GET /v1/projects/:project_id/cases { project_id: "default", status: "open" }

The output

The agent returns suppressions sorted by risk: broad pattern, recent matches, affected users, and recommended action.

Setting it up

No extra instrumentation required beyond errors. Keep suppression reasons specific so future agents can evaluate intent.

Variations

  • “Expire any suppression that has not matched in 30 days.”
  • “Show suppressed errors after the last deploy.”
  • “Turn this into a weekly oncall hygiene check.”

Related recipes

ops 1 minute

Stop noisy errors from paging you — in plain English

Suppress third-party SDK timeouts, ad-blocker errors, and other false-positives by describing them. No regex required.

debugging 10 seconds

Find the bugs 5 people hit but no one reported

Surface real errors that affect multiple users but never get filed as tickets. The biggest source of silent churn.

debugging 2 minutes

Rank errors by revenue impact, not raw count

Multiply users-affected by their plan ARR to surface the bugs costing real money. Stop triaging by event volume.

Try this recipe in your own agent.

Ask your agent to adapt the starter prompt to your saved signal map and live events, then run it against your data.

Install agentry.sh/install.md for me
Agent will onboard itself and then your app
← all recipes