Triage production incidents by choosing useful metrics, logs, traces, queue signals, database evidence, request ids, and alerting strategies.
Interactive scenario
Use the controls below. Feedback appears immediately and final scores stay in this browser.
Concept notes
Observability Incident Triage is focused practice for Production observability, incident triage, metrics, logs, traces, and alerts. It explains why each answer is safe, risky, or production-ready.
Incident response is a race against uncertainty. This game gives you a pager, a symptom, and a handful of possible signals so you can practice finding the truth without drowning in noise.
Observability is the ability to ask useful questions about a running system. During incidents, the best signals connect user symptoms, recent changes, failing dependencies, and concrete request paths.
Metrics show shape and impact, traces show where time went, logs provide event detail, request IDs connect user reports, and alerts should be tied to actionable user-facing risk.
Use the main site for deeper reading after playing.
Use tools from the main site when you want to inspect real inputs.
Short answers for how this game fits backend interview and study practice.
Logs are useful, but incidents usually need metrics for impact, traces for path timing, and correlation IDs to connect events across services.
A good alert is actionable, has clear owner expectations, and usually represents user impact or a durable risk to user impact.
Top 10 scores for the current ruleset. No account required.
Loading leaderboard...
Finish the game to load your latest local score.