Alert / Trigger#

Describe what triggers this runbook (e.g., alert name, error condition, scheduled event).

Impact#

• Severity: Critical | High | Medium | Low
• Affected services: List affected services
• User impact: Describe impact on end users

Prerequisites#

• Required access or permissions
• Tools needed
• Relevant dashboards or monitoring links

Procedure#

Step 1: Assess the Situation#

Describe what to check first.

# Example diagnostic command
kubectl get pods -n production

Step 2: Apply the Fix#

Describe the remediation steps.

# Example fix command
kubectl rollout restart deployment/service-name -n production

Step 3: Verify Resolution#

Describe how to confirm the issue is resolved.

Rollback#

If the fix doesn't work or makes things worse:

1. Rollback step 1
2. Rollback step 2

Post-Incident#

• Update incident timeline
• Notify stakeholders
• Schedule post-mortem if severity warrants it