CPR.co
For Admins

Sentry alerts — what to do when one fires

On-call playbook for triaging, silencing, and resolving Sentry error alerts.

Sentry watches for unhandled errors in production and alerts the on-call engineer when something is wrong. The full ops playbook lives at docs/SENTRY-OPERATIONS.md — this article is a quick orientation.

When an alert fires

Triage steps
  1. 1Open the alert link in Slack — it goes straight to the Sentry issue.
  2. 2Read the title and the most recent stack trace. Identify the user-impacting symptom (booking failed, email did not send, page crashed, etc.).
  3. 3Check the issue page for a Session Replay video if one exists — they are recorded for 100% of error sessions and show exactly what the user did.
  4. 4Decide: drop everything (P0 — payments / auth / data loss), schedule for today (P1 — broken feature affecting a real user), or backlog (P2 — noise or rare path).
  5. 5Update the issue status in Sentry — Resolved, Ignored, or assigned to a teammate.

Useful Sentry features

  • Session Replay — 1% of normal sessions + 100% of error sessions, with PII masked
  • User feedback widget — students can report what they were trying to do
  • Tunnel route at /monitoring — bypasses ad blockers so error reports actually reach Sentry
  • Source maps — every release uploads sourcemaps so stack traces show real file/line numbers
⚠️
Important: Do NOT ignore an alert without reading it. The thresholds are tuned to fire only on real, actionable issues. Repeated ignores create alert blindness.
💡
Tip: If an error is genuinely noise (a known third-party flake, a bot scanning, etc.), use Sentry's Ignore option with a reason rather than just resolving — that way it stops paging but you keep the audit trail.
ℹ️
Note: See docs/SENTRY-OPERATIONS.md for the full SOP — alert routing, on-call rotation, runbooks per error class, and the monthly noise-pruning ritual.

Was this article helpful?

Still need help?

We're here for you — call or email us any time during business hours.

Mon–Fri 8am–5pm Central Time

💬Chat with us