Your Runbook Has No Deadlines: Budgeting Every On-Call Step Before the Page Goes Late

Описание и применение

В статье описывается, как добавить явные временные лимиты к каждому шагу runbook, чтобы избежать перерасхода времени и соблюсти SLA.

Задача

Runbooks often lack explicit time budgets for each step, causing incidents to overrun their escalation SLAs.

Результат

Runbooks with explicit time budgets reduce incident duration and align escalation with SLAs.

Рабочий процесс

• Define a time budget, stop condition, and timeout action for each runbook step.
• Sum the declared budgets and compare the total plus escalation hold against the SLA.
• If the total exceeds the SLA, adjust budgets or steps before incidents occur.
• Use a validator script to enforce required fields and budget limits.
• Review and argue the budgets in a code‑review style to ensure defensibility.

Доказательства

Most runbooks I read fail for a boring reason: nothing in them has a deadline.

Источник

Treat each runbook step as a small contract with three fields: a time budget, a stop condition, and a timeout action.

Источник

Worst case here is 120 + 90 + 300 + 240 = 750 seconds, which leaves 150 seconds of slack against a 900-second target.

Источник

The script is small on purpose: it validates required fields, sums the declared budgets, and refuses to pass when the total plus the escalation hold exceeds the SLA you pass in.

Источник