# Release marker missing in monitoring: first 30 minutes 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.
- [ ] 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.
- [ ] FM-02 Check the edge network's request logs for the failing path when internal application and proxy logs show no errors.
- [ ] FM-03 Check for indexes dropped by post-deployment migrations when database load climbs without a matching application deploy.
- [ ] FM-04 If draining the canary does not improve the metrics, move on to the next change in the list.
- [ ] FM-05 Roll back the change whose time matches the start of impact, through the rollback control of its own deploy path.
- [ ] FM-06 Add a manual dashboard annotation for each change found and each action taken, with its time.
- [ ] FM-07 Post a status update that names the failing workflow, such as artifact uploads, and the share of failing requests.