Generate runbook steps from this incident scenario. Examples: Scenario: Database connection pool exhausted Steps: 1. Check connection count: SELECT count(*) FROM pg_stat_activity 2. Identify long-running queries: SELECT * FROM pg_stat_activity WHERE state != idle ORDER BY query_start 3. Kill stale connections: SELECT pg_terminate_backend(pid) 4. Restart affected pods: kubectl rollout restart deployment/api 5. Verify recovery: Check /health endpoint and connection metrics Scenario: Memory usage spike causing OOM kills Steps: 1. Identify affected pods: kubectl get pods with OOMKilled 2. Check memory trends: Query Prometheus for container_memory_usage 3. Take heap dump if safe: kubectl exec -it pod -- jmap -dump 4. Increase limits temporarily: kubectl set resources deployment/app 5. Scale horizontally: kubectl scale deployment/app --replicas=5 Incident scenario: {{incident_scenario}} Affected system: {{system}}
Runbook Action Steps Generation
Generate runbook action steps from incident descriptions.
3 copies0 forks
Details
Category
CodingUse Cases
Runbook documentation creationIncident response automationOn-call knowledge transfer
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared