RUNBOOK-EDI

SRE / DevOps concept Runbook for EDI operations.

Definition

An EDI runbook is a step-by-step procedure to respond to a recurring signal: '997 pending counter exceeds 100', 'AS2 gateway returns 503', 'CFDI hash mismatch'. Includes: diagnostic commands, Splunk/Datadog queries, contacts, escalation. Stored close to paging (PagerDuty, Opsgenie). Updated at every incident.

Origin

Practice born in telecom NOCs, adopted by SREs from the 2010s.

Example in context

Alert "997 pending > 100" → runbook: 1. kubectl get pods -n edi, 2. log query "997 timeout", 3. ping AS2 partner, 4. escalate VAN if > 30 min.

Related terms

• On-call rotation — operators executing the runbook.