SRE runbook template: diagnosis, bounded action, and recovery
Download a Markdown runbook template and follow a database connection example that separates symptoms, mitigation decisions, and verified recovery.
Search titles and article text.
Download a Markdown runbook template and follow a database connection example that separates symptoms, mitigation decisions, and verified recovery.
Define inputs, permissions, idempotency, verification, and stop conditions for one operational capability before expanding its authority.
Connect AI-assisted diagnosis to bounded runbooks, explicit approval gates, and independent recovery checks. Start with a practical SRE rollout checklist.
Define the action, contain its scope, and verify what changed at the destination.
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
Separate incident coordination from mitigation authority, compare competing actions, and use a worksheet that preserves decisions and verification.
Build repeatable cases and check recovery independently, with a runnable Python grader.
Check agent status, terminal persistence, and recovery before adopting Herdr.
A design guide for an incident assistant that handles duplicate events, partial failures, and reviewed AI summaries across tools.
Design incident channels, bot actions, evidence links, and a fallback path that still works when the chat system is unavailable.
Use language-model assistance for evidence review, draft communication, and practice, with a clear boundary around production decisions.
Prepare evidence, reconstruct the timeline, examine contributing conditions, and choose follow-up proportionate to the incident.