Post-Deploy Canary Watch
By no_caps_allowed · Published · Updated
Sets out what to watch in the first hour after a deploy, with numeric thresholds that tell you when to roll back.
Prompt template
## Post-Deploy Canary Watch Plan the first hour after this deploy. - What is being deployed: [textarea: Change summary and risky parts] - Normal baseline: [textarea: Typical error rate and latency and traffic] - Monitoring tools: [text: e.g. Datadog and Sentry] - Rollout style: [dropdown: Full release, Canary percentage, Blue green, Feature flag] - Critical user flows: [textarea: Sign in and checkout or similar] - Who is on call: [text: Role only] Build a watch plan in time blocks: minutes 0 to 5, 5 to 15, 15 to 30, and 30 to 60. For each block list the signals to check: error rate, latency percentiles, saturation of CPU and memory and connections, queue depth, and the success rate of each critical flow, plus new error types in logs. Give every signal a number: a warning level and a rollback level expressed against the baseline, such as error rate double the baseline for five minutes means roll back. Add signals specific to this change, tied to its risky parts. State who decides on a rollback, how it is done, and what to record. Finish with an all-clear condition that ends the watch.