How to run live monitoring after a release
The first 7 days post-release are when reality contradicts the staging environment. Live monitoring is the structured check that catches it.
Why it matters
The cost of catching a bad release in week one is small. The cost of catching it in week three is huge, by then customers have integrated the broken behaviour into their workflow. Live monitoring forces a structured triage early so the rollback / fix-forward / continue call is made on data, not intuition.
Step by step
- Day 0. Health Sentinel agent runs the technical health check (errors, latency, anomalies).
- Day 1. Live Support agent triages customer-facing impact (bugs raised, support tickets, sentiment).
- Read the Live Support kit. Customer impact statement, FAQ, support macro, recommendation (continue / watch / rollback).
- Decide. If recommendation is "rollback", do it inside the agreed window. If "watch", set the next check date. If "continue", note the win.
- Day 3 + Day 7. Re-run Live Support if the original recommendation was "watch".
- Open follow-up RAID rows. For anything that needs tracking past the monitoring window. The agent can auto-open these.
What good looks like
- Health + Live Support runs done in first 24h
- One owner for the continue/watch/rollback call
- Customer-facing FAQ + support macro published
- Follow-up RAID items raised for anything outliving the window
- Decision reasoned in writing, not Slack
How Tenhaw runs this
Two agents run the post-release window. Health Sentinel handles the technical SRE check (errors, latency, anomalies); Live Support handles the customer-facing triage (impact statement, FAQ, support macro, continue/watch/rollback). Live Support can auto-open follow-up RAID rows for issues that outlive the monitoring window.
- Tenhaw Health Sentinel AI agent
- Tenhaw Live Support AI agent
- Tenhaw RAID Logs auto-population
In Tenhaw → story in Live Monitoring stage. Live Support auto-selects on this stage from the AI panel.
Run this in your team
The Tenhaw product enforces every rule in this playbook so it doesn't sit on a wiki gathering dust. Try Tenhaw or book a working session with the founder.