SynfraCore
Synfracore
Start Learning
Navigation

Academies

Platform

RoadmapsLabsCertificationsInterviewPYQsAI AssistantCareer
Start Learning Free Learning Roadmaps

Incident ManagementCheatsheets

Quick reference — commands, syntax, and patterns

📄
Last updated Jul 2026
Expert Content

Incident Response Runbook Template

INCIDENT DECLARED
  - Severity: P1 / P2 / P3
  - Incident Commander: [name]
  - Start time: [UTC]
  
IMMEDIATELY
  1. Join incident Slack channel #incident-YYYY-MM-DD
  2. Start incident timeline doc
  3. Notify stakeholders (P1: CTO, VP Eng; P2: Eng Manager)

MITIGATION FIRST
  4. Can we rollback? → helm rollback / kubectl rollout undo
  5. Can we failover? → switch traffic to backup region
  6. Can we disable the feature? → feature flag off
  7. Can we scale? → increase replicas / autoscaling
  
INVESTIGATION PARALLEL
  8. Check dashboards: Datadog/Grafana error rate, latency, saturation
  9. Check logs: Kibana/Splunk for error patterns
  10. Check recent deploys: last 2 hours of changes
  11. Check infra: node status, disk, memory pressure
  
RESOLUTION
  12. Confirm metrics back to normal
  13. Notify stakeholders: "Resolved at [time]"
  14. Keep channel open 30 min for stability monitoring
  
POST-MORTEM
  15. Schedule within 48 hours (P1) or 1 week (P2)
  16. Write timeline, root cause, action items
  17. Present to engineering team
Share:
Join our Community
Daily tips, job alerts, interview help — join engineers learning together
Up Next
📝
Incident ManagementNotes
Key takeaways, tips, and important points to remember
Also Worth Exploring
← Back to all Incident Management modules
CertificationNotes