An alert paged a team that left eighteen months ago. Design alert routing and escalation so this cannot happen.

Routing rots because orgs change faster than configs. The senior answer treats ownership as data resolved from a catalog at fire time, with drift detection on the routing itself.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Routing rots because orgs change faster than configs. The senior answer treats ownership as data resolved from a catalog at fire time, with drift detection on the routing itself.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25

UP NEXT ON YOUR JOURNEY

Next in this trackEveryone has runbooks and nobody opens them mid-incident. What makes a runbook people actually use?Next in this trackHow long should an on-call rotation be, and how do you hand over without losing context?Next in this trackWalk me through facilitating the post-incident review after a severe outage. How do you keep it blameless but not toothless?

DISCUSSION · 0

Nothing here yet. Say how you would answer it.