# Release marker missing in monitoring: pre-release checklist

Source: https://releasefailures.com/incidents/release-marker-missing-in-monitoring/
Content version: 1.0.0
Verified on: 2026-10-21
Licence: CC BY 4.0

Definition: Responders cannot see which deploy correlates with the change in metrics.
- [ ] PR-01 Confirm the HTTP router deploy writes a deployment annotation to the monitoring dashboards in staging before the production deploy. (test class: Configuration and environment tests)
- [ ] PR-02 Confirm each post-deployment migration run writes its own dashboard annotation, separate from the canary deployment annotation. (test class: Configuration and environment tests)
- [ ] PR-03 Confirm a push to the service discovery system writes a change event that appears on the same dashboards as deploy annotations. (test class: Configuration and environment tests)
- [ ] PR-04 Validate every new service record against the service discovery schema before it is pushed. (test class: Configuration and environment tests)
- [ ] PR-05 After each HTTP router deploy, run a scripted artifact upload larger than the edge worker memory buffer and confirm it returns success. (test class: Synthetic monitoring)
- [ ] PR-06 Route failures of the scripted artifact upload check to an alert that names the HTTP router. (test class: Synthetic monitoring)
- [ ] PR-07 List the post-deployment migrations pending for the release in the canary report. (test class: Canary and progressive delivery checks)
- [ ] PR-08 Chart in-flight background jobs for canary and baseline on a dashboard that shows every annotated change. (test class: Canary and progressive delivery checks)