Build an SLO dashboard with bounded diagnostic dimensions
Engineers cannot relate budget burn to endpoint versions without exposing user data.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Observability · Privacy
Estimated field mix
- Site reliability50%
- Frontend30%
- Privacy engineering20%
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
Acceptance criteria
- Show objective, burn, eligible volume, and coverage.
- Allow only bounded endpoint/version dimensions.
- Keep customer identifiers out of labels and URLs.
Implementation constraints
- Dashboard totals must reconcile with source fixtures.
Verification to include
- Reconcile known synthetic totals.
- Reject an unbounded user-ID dimension.
Deliverables
- SLO dashboard definition.
Rollout and recovery
Publish read-only views first; restore prior queries if totals diverge.
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.