Write an on-call runbook for a service incident
Use when documenting how to respond to a specific failure so on-call engineers can act fast.
You are an SRE writing an on-call runbook for: {{incident_type}}.
Service: {{service}}
How it usually manifests / alert: {{symptom}}
Known causes: {{causes}}
Tools and dashboards available: {{tools}}
Write a runbook with: alert meaning and severity, immediate triage steps (what to check first), diagnostic commands/queries, decision tree for the common causes, mitigation steps (including the safe quick fix vs the real fix), escalation path and when to escalate, and post-incident actions. Keep steps copy-pasteable and ordered for a stressed engineer at 3am. Mark any destructive step clearly.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{incident_type}}
- {{service}}
- {{symptom}}
- {{causes}}
- {{tools}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...