Alert Volume Budget

Per-week alert budget. Enforces tuning discipline.

What an alert volume budget is

A team-level cap on alerts per on-call shift. Above the cap, the rotation is over capacity and alerts must be retired or escalated.

Typical budgets: 5 pages per shift for sev1, 15 per shift total. Above that, response quality drops and engineers burn out.

The budget is a forcing function. Going over the budget means you cannot ship a new alert without retiring an old one.

Measure actual versus budget

Pull alert history weekly. Count pages per shift, per team, per severity.

Plot against the budget on a dashboard the team owns. Red when over budget for 2 weeks running.

Break it out by alert source. The top 3 sources usually account for 70% of pages.

When you go over budget

Mandatory cleanup before any new alert ships. The team picks 3 alerts to retire or retune.

If the team cannot reduce volume, the rotation is understaffed. Add headcount or shrink scope.

Don't ignore the budget. The next escalation is attrition; that costs more than the cleanup.

How to set the budget

Survey on-call: how many pages per shift feel sustainable. Pick the median.

Industry baseline: 2 pages per shift is comfortable, 5 is the upper limit, 10+ is burnout territory.

Tighter for smaller rotations. A 3-person rotation cannot absorb 10 pages a shift; a 10-person rotation can.

Roll out the budget this quarter

Publish the current page count and the proposed budget. Get team sign-off.

Hold a cleanup sprint to get under budget. Retire or retune 5-10 alerts.

Make budget compliance a recurring metric. If you stay over budget for 2 quarters, the rotation is broken structurally.