The full automation library
Every trigger, and the jobs teams hand it. None of these are fixed: they are starting points you rewrite in your own words.
Every deploy, just after rollout
Watch the canary
Read the golden metrics and flag any anomaly on any server. Watch the canary while it is at 1% and tell me before we widen it.
Lands in #deploys in Slack
Compare against the last good window
Compare error rate and p99 against the same window before this deploy. If anything regressed, name the commit that did it.
Lands in #deploys in Slack
Check the neighbours
Check that every service depending on this one is still healthy, not just the one that shipped.
Lands in PagerDuty incident note
A pull request is opened
Infra review
List the infrastructure modifications that need to be made before this merges. If there are none, comment LGTM. Otherwise share the complete list of changes in detail.
Lands in Comment on the pull request
Latency and memory
Flag anything in this pull request that is going to add latency or memory. Call out queries that will run without an index.
Lands in Comment on the pull request
Docs that go stale
Check whether this changes an alert threshold or a runbook step, and say which docs are now wrong.
Lands in Linear ticket
Every 24 hours
Memory drift
Check memory usage for the pods and flag it if it is climbing. Ignore pod restarts, they reset the counter and are not the signal I care about.
Restart-aware, so a nightly redeploy does not mask a real leak.
Lands in #sre-daily in Slack
Yesterday, grouped by cause
Summarize every alert that fired in the last day, grouped by root cause, and tell me which ones were noise.
Lands in #sre-daily in Slack
Disk headroom
Find volumes that will cross 80% within a week at their current growth rate, and say what is filling them.
Lands in Linear ticket
Every hour
Payload size creep
Check the logs and tell me if there is any increase in large payloads being dumped. If there is, work out which caller changed.
Lands in #platform in Slack
Queue not draining
Watch queue depth on the payments worker. Tell me if it is growing rather than draining, and how far behind it is.
Lands in #platform in Slack
An alert fires
Run the database checklist
Before paging anyone, check replication lag, connection pool, slow query log, and recent migrations. Attach whatever you find to the alert.
Lands in PagerDuty incident note
Have we seen this before
Work out whether this is the same failure as the last three times this alert fired. If it is, say so and link them.
Lands in #incidents in Slack
An inbound webhook
Probe the endpoint
POST to /v1/quote with the sample payload and check the response comes back with a price field. If it does not, find out what changed.
Lands in #platform in Slack
Assemble the customer picture
Take the customer ID in the payload and assemble everything we know about their last failed request.
Lands in Reply to the webhook
