noCV
BSLO-104 · Compute and alert

Keep missing telemetry distinct from successful service

Practice briefBugIntermediate

A metrics outage produces an empty query that the dashboard renders as healthy.

Focused work estimate
2h + prerequisites
Priority in the scenario
High
Engineering practice
Monitoring

Estimated field mix

  • Site reliability80%
  • Frontend20%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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

  • Represent no data separately from zero failures.
  • Display data freshness and coverage.
  • Alert on measurement failure independently.

Implementation constraints

  • Unknown reliability cannot consume zero budget by default.

Verification to include

  • Show healthy complete telemetry.
  • Drop a source stream and display unknown coverage.

Deliverables

  • Missing-data handling.

Rollout and recovery

Enable measurement alerts before relying on budget policy.

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.