Compute completion latency from consistent event pairs
Latency is measured from different start events across client versions.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Observability · Time handling
Estimated field mix
- Site reliability60%
- Data engineering40%
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
- Specify start and completion event semantics.
- Reject negative or unmatched durations.
- Track excluded samples and instrumentation version.
Implementation constraints
- State clock assumptions explicitly.
Verification to include
- Compute known synthetic durations.
- Detect clock skew and unmatched completion events.
Deliverables
- Latency indicator implementation.
Rollout and recovery
Run both definitions during comparison; retain the prior dashboard for diagnosis.
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.