Code Room
On-callMedium
Question
Your service has been burning its error budget fast this week (SLO at risk) and an alert flags it, but the team has features queued to ship. As on-call and reviewer, how do you handle it?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
Learn the concepts
Loading whiteboard…
Run or narrate your approach, then ask the coach.