Tag: incident-response

Operational runbook for LLM production incidents: hallucination events, model outages, cost spikes, safety failures, and degraded quality. Includes severity levels, escalation paths, diagnostic steps, and recovery procedures.

Runbook for warming caches after deployment, restart, or incident: identify hot keys, preload strategies, progressive warmup, health checks, and rollback procedures with code examples and automation scripts.

A step-by-step playbook for responding to security incidents involving unauthorized data access, from initial detection through notification and remediation.

Runbook for rolling back failed deployments safely: rollback triggers, Kubernetes rollback, blue-green deployment rollback, canary rollback, database migration rollback, verification steps, and post-rollback procedures with code examples for kubectl, Helm, and ArgoCD.

A policy template that defines how alerts are configured, routed, escalated, and reviewed across services and infrastructure.

A standardized runbook for responding to alerts: triage, diagnosis, mitigation, resolution, and post-incident steps with escalation paths.

A template for incident response covering severity classification, roles, detection, containment, eradication, recovery, and post-incident review procedures.

A step-by-step playbook template for handling security incidents.

A template for security incident response covering detection, classification, containment, eradication, recovery, communication, and post-incident review.

A reusable template for operational runbooks: incident response, deployment procedures, and routine tasks.

A practical playbook for on-call engineers: triage, escalation, communication, and postmortems. Reduce MTTR and build a resilient incident response culture.

A practical guide to incident response: declaring incidents, building an incident command structure, communication protocols, and reducing mean time to resolution with structured processes.