Attach a release marker to bounded operational telemetry
An error spike starts near a deploy, but the dashboard has no release event or stable artifact link. Engineers compare screenshots and guess which change was live.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Observability · Cardinality · Release diagnostics
Estimated field mix
- Site reliability60%
- Platform 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 scheduling service has an API, a worker, and PostgreSQL. Releases use immutable images on two application instances. The team needs compatibility checks, staged traffic, and a rehearsed rollback without introducing a new orchestration platform.
Setup prerequisites
- HTTP health checks
- CI pipelines
- Database migrations
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ROLL-101 · Display the exact release identity in diagnostics
- ROLL-102 · Separate liveness from database readiness
- ROLL-103 · Refuse deploys with incomplete runtime configuration
- ROLL-104 · Keep old API instances working during a column rename
- ROLL-105 · Prevent two release jobs from overwriting the same environment
- ROLL-106 · Base canary decisions on enough comparable requests
Acceptance criteria
- Emit a release event with environment, deployment ID, artifact digest, and stage outcome.
- Link stage failures to sanitized diagnostic references.
- Keep request bodies, secret values, and arbitrary commit messages out of metric labels.
Implementation constraints
- Store high-cardinality release details in events; use bounded dimensions for metrics.
Verification to include
- Trace a simulated canary abort from its marker to its release manifest.
- Inject secret-like fixture metadata and verify the telemetry projection excludes it.
Deliverables
- Release event schema and incident dashboard query
Rollout and recovery
Add markers without changing alert thresholds; disable the new event sink if it delays release decisions.
Value of the work
For the engineer: Practice release contracts, compatibility windows, measurable canaries, and incident decisions on a modest application topology.
For the team: Review whether an engineer can make deployments diagnosable and reversible while identifying when rollback is unsafe.
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.