Your Pager Is Lying to You: Fixing On-Call, Alerts, and MTTR for Real

March 3rd, 2026 at 11am ET

You’re not the only one who feels like your on-call rotations are fragile, alerts are loud, and incidents take longer than they should, even in dev and QA.

Two practicing SREs talk about what’s wrong with modern incident response in this live session. They talk about alert noise, brittle routing rules, disconnected tools, and on-call schedules that fall apart as soon as someone leaves the team.

Key Takeaways:

• Fewer alerts lead to faster resolution – Reducing alert noise and focusing on actionable signals improves response speed and helps teams identify real issues more quickly.
• Clear ownership matters more than more tooling – Well-defined responsibility and escalation paths reduce confusion and delays during incidents, even in complex environments.
• Incident response needs to work beyond production – Applying the same discipline to dev and QA incidents improves release velocity, quality, and overall system reliability.
• Streamlined incident workflows shorten MTTR – Reducing fragmentation across tools leads to faster, more predictable incident resolution.
• Small changes can significantly improve on-call health – Incremental improvements to alerting, routing, and workflows can reduce burnout without adding heavy process or overhead.