Loading...
When a system fails, SREs are on the hook. They face high "operational load" and cognitive "overload" from the high-stress, complex debugging required to restore service.
# Diagnosing and Resolving Live Site Incidents ## Problem Context When a system fails, SREs are on the hook. They face high "operational load" and cognitive "overload" from the high-stress, complex debugging required to restore service. ## Solution Pattern: incident-co-pilot The "Incident Co-Pilot": Analyzes alerts, suggests troubleshooting steps (RCA), and drafts postmortem reports from an incident timeline. ## Prompt Template Act as an DevOps & SRE Engineer. When a system fails, SREs are on the hook. They face high "operational load" and cognitive "overload" from the high-stress, complex debugging required to restore service. The "Incident Co-Pilot": Analyzes alerts, suggests troubleshooting steps (RCA), and drafts postmortem reports from an incident timeline. **Instructions:** 1. Understand the problem context 2. Apply the solution pattern described above 3. Provide step-by-step guidance 4. Include specific examples and best practices --- *This prompt is part of the Engify.ai research-based prompt library. Customize it for your specific context and needs.*
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Plan effective sprints with capacity planning and risk assessment
Facilitate effective sprint planning sessions with your team
Create comprehensive performance reviews for engineering team members