Operational Runbooks
Incident Response Runbook
1. Confirm severity and affected users. 2. Capture timestamp, URL, request id, and safe logs. 3. Check `/api/health` and `/api/ready`. 4. Disable risky feature flags if relevant. 5
Use this when you need a repeatable operational procedure.
- Confirm severity and affected users.
- Capture timestamp, URL, request id, and safe logs.
- Check
/api/healthand/api/ready. - Disable risky feature flags if relevant.
- Decide fix-forward or rollback with approval.
- Record the incident and follow-up System QA issues.
Do not paste secrets, tokens, passwords, private imports, or customer-sensitive data into incident notes.
Developer Details
- Source
- apps/docs/content/operational-runbooks/incident-response.md
- Owner
- Platform / Operations
- Status
- Current
- Module
- Operational Runbooks
- Related route
- None