Implement multi-window error-budget burn calculations
A brief spike pages the team while a slower sustained incident passes unnoticed.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Alerting · Time-series analysis
Estimated field mix
- Site reliability70%
- Data engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional checkout service reports process uptime while customers experience failed orders and slow confirmations.
Setup prerequisites
- Create synthetic request and order-event traces plus a local query or metrics fixture; no production telemetry required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Calculate burn against the declared objective.
- Require aligned short and long windows for the chosen alert.
- Handle window edges and low sample counts explicitly.
Implementation constraints
- Thresholds are scenario assumptions, not universal defaults.
Verification to include
- Trigger on sustained synthetic burn.
- Avoid paging for an isolated low-volume failure under the documented policy.
Deliverables
- Burn-rate queries and fixtures.
Rollout and recovery
Run alerts without notifications locally before operational adoption.
Value of the work
For the engineer: Practice SLI semantics, alert evaluation, and reliability tradeoffs.
For the team: Align reliability discussions with customer outcomes and explicit measurement limits.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.