BestPromptFinder

On-Call Runbook for a Service or Common Alert

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

Write an on-call runbook someone half-awake at 3 a.m. can follow. Service or alert: [e.g. "API error rate above 5%" / "payment webhook failing" / "disk 90% full"] Architecture: [components, hosting, where logs and dashboards live] Access the on-call person has: [ ] Known causes from past incidents: [list] Who to escalate to: [roles, not personal numbers] Runbook format: 1. What this alert means and the user impact, in two lines. 2. First five minutes: check these dashboards and commands, in order, each with what "normal" looks like. 3. Decision tree: if you see X, do Y. One branch per known cause, each with exact, safe commands. 4. Safe mitigations (restart, scale up, roll back, disable a feature flag) with how to undo each. 5. When and how to escalate, and the status-update message template for users or the team. 6. After the incident: what to record. Rules: mark every destructive command with a warning and a confirmation step; no secrets in the runbook; placeholders for hostnames and dashboard links.

Why this prompt

• Hand-picked, editorially reviewed prompt
• Written for Claude, ChatGPT, Gemini

Source

Created by BestPromptFinder — editorial prompt, not user-generated. See our content & source policy.

Related Coding prompts