Release marker missing in monitoring: pre-release and first 30 minutes checklists

Responders cannot see which deploy correlates with the change in metrics.

The pre-release checklist maps each item to a test class from the incident page. The first-30-minutes checklist covers detection, containment, the rollback decision and customer communication.

8 pre-release items · 7 first-30-minutes items · verified 2026-10-21

Pre-release checklist

PR-01Confirm the HTTP router deploy writes a deployment annotation to the monitoring dashboards in staging before the production deploy. config
PR-02Confirm each post-deployment migration run writes its own dashboard annotation, separate from the canary deployment annotation. config
PR-03Confirm a push to the service discovery system writes a change event that appears on the same dashboards as deploy annotations. config
PR-04Validate every new service record against the service discovery schema before it is pushed. config
PR-05After each HTTP router deploy, run a scripted artifact upload larger than the edge worker memory buffer and confirm it returns success. synthetic
PR-06Route failures of the scripted artifact upload check to an alert that names the HTTP router. synthetic
PR-07List the post-deployment migrations pending for the release in the canary report. canary
PR-08Chart in-flight background jobs for canary and baseline on a dashboard that shows every annotated change. canary

First 30 minutes

FM-01List every change from the last 24 hours across all deploy paths: application deploys, HTTP router deploys, post-deployment migrations and service discovery pushes.
FM-02Check the edge network's request logs for the failing path when internal application and proxy logs show no errors.
FM-03Check for indexes dropped by post-deployment migrations when database load climbs without a matching application deploy.
FM-04If draining the canary does not improve the metrics, move on to the next change in the list.
FM-05Roll back the change whose time matches the start of impact, through the rollback control of its own deploy path.
FM-06Add a manual dashboard annotation for each change found and each action taken, with its time.
FM-07Post a status update that names the failing workflow, such as artifact uploads, and the share of failing requests.

Download the checklist

Pre-release checklist (Markdown)1.6 KB · v1.0.0
First 30 minutes checklist (Markdown)1.2 KB · v1.0.0

Only in this checklist

PR-05 is the only item among 5 published checklists in this group that relies on synthetic monitoring: After each HTTP router deploy, run a scripted artifact upload larger than the edge worker memory buffer and confirm it returns success.

Questions

What should be checked before a release to prevent Release marker missing in monitoring?

8 pre-release items, PR-01 to PR-08. PR-01: Confirm the HTTP router deploy writes a deployment annotation to the monitoring dashboards in staging before the production deploy.

Is there a rollback plan for Release marker missing in monitoring?

The first-30-minutes checklist has 7 items. FM-01: List every change from the last 24 hours across all deploy paths: application deploys, HTTP router deploys, post-deployment migrations and service discovery pushes.

What should a team do in the first 30 minutes after Release marker missing in monitoring is detected?

Which configuration checks apply to Release marker missing in monitoring?

PR-01: Confirm the HTTP router deploy writes a deployment annotation to the monitoring dashboards in staging before the production deploy. PR-02: Confirm each post-deployment migration run writes its own dashboard annotation, separate from the canary deployment annotation. PR-03: Confirm a push to the service discovery system writes a change event that appears on the same dashboards as deploy annotations. PR-04: Validate every new service record against the service discovery schema before it is pushed.

Is a Release marker missing in monitoring checklist still needed if deployment is automated?

Yes. Automation runs the steps; the checklist names what the tests must cover: configuration and environment tests, synthetic monitoring and canary and progressive delivery checks.

Which pipeline stages does the Release marker missing in monitoring checklist cover?

The pre-release items map to the pre-deploy and post-deploy stages.