Guide Your Team to Resolution.
Stop guessing during incidents. Create detailed Playbooks to provide step-by-step resolution instructions and link them directly to your alerts.
# Database High CPU ## Severity: Critical ## Owner: @backend-team ### 1. Diagnosis Check the connection count graphs. If connections > 1000, it might be a connection leak. ### 2. Immediate Action Run the following command to identify top consumers: `SELECT * FROM pg_stat_activity ORDER BY duration DESC;` ### 3. Mitigation If a bad migration caused this, adhere to the [Rollback Procedure](link/to/rollback).
Actionable Knowledge Base
Don't let knowledge get lost in Slack threads. Document your incident response procedures in a central repository that is always up-to-date and accessible.
- Markdown Support
- Link directly to Alerts
- Version Controlled
Instant Context
Engineers are directed to the exact Playbook they need the moment an alert triggers.
Standardized Process
Ensure every incident is handled consistently, regardless of who is on call.
Collaborative
Edit playbooks together in real-time. Keep your reliable sources of truth valid.