Write an SLO interpretation guide for low-traffic periods
A single failure overnight produces a dramatic percentage without explaining the sample size.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Technical writing · Reliability
Estimated field mix
- Site reliability100%
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.
- BSLO-101 · Define eligible checkout attempts and successful completion
- BSLO-102 · Deduplicate retried checkout attempts in indicator calculations
- BSLO-103 · Compute completion latency from consistent event pairs
- BSLO-104 · Keep missing telemetry distinct from successful service
- BSLO-105 · Implement multi-window error-budget burn calculations
- BSLO-106 · Separate dependency failure from the customer-facing objective
- BSLO-107 · Define release actions for exhausted error budget
- BSLO-108 · Build an SLO dashboard with bounded diagnostic dimensions
- BSLO-109 · Rehearse an objective change without rewriting historical results
Acceptance criteria
- Display eligible event count with the ratio.
- Explain low-volume uncertainty.
- Document when to inspect individual synthetic traces.
Implementation constraints
- Avoid promises of perfect reliability.
Verification to include
- Interpret one failure in a small sample.
- Distinguish zero traffic from a healthy measured window.
Deliverables
- SLO interpretation guide.
Rollout and recovery
Link guidance from dashboards and alert descriptions.
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.