What MTTD misses
Separate detection from response and find delays that an improving average can conceal.
Analysis of AI in production, reliability metrics and how engineering teams work.
Separate detection from response and find delays that an improving average can conceal.
The permissions, state and recovery paths an agent needs when its tool calls can change a running service.
When alerts share a headline, one successful repair can hide a second failure. Follow the remaining symptom through the group, the trial and the next responder.
The repair is ready, but an unrelated feature is in the same package. An error-budget policy needs a way to assess the repair alone or decide on a scoped exception.
Follow late invoices from a shared queue to the planning meeting. Find which approval, access and engineering commitments let the service owner recover them.
Two workers share a name. A blameless review can show why one looked like the other and test whether a change helps the next responder choose.
Moving customer overrides tidies a file. Retiring an unused override can simplify the service. Follow the settings through investigation, migration and recovery to tell the difference.
A misrouted ticket shows what an automated decision can hide and what a reviewer needs to put the request back on track.
A backup needs access, knowledge, authority and room for the work. Rehearse the transfer before leave so the service has a dependable path.
Relief after an interrupted night needs coverage and moved commitments. Then follow the recurring demand so the next week asks less of the same people.
Reliability work needs time, usable agreements and decisions that remove obstacles. Follow what a leader can change before, during and after an incident.