klaviyo-incident-runbook

# Klaviyo Incident Runbook ## Overview Rapid incident response for Klaviyo API outages and integration failures: quick triage, decision trees, mitigation steps, and postmortem templates. ## Severity Levels | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | Complete outage | <15 min | All Klaviyo API calls returning 5xx | | P2 | Degraded service | <1 hour | 429 rate limiting, high latency | | P3 | Minor impact | <4 hours | Webhook delays, single endpoint errors | | P4 | No user impact | Next business day | Monitoring gaps, deprecation warnings | ## Quick Triage (Run Immediately) ```bash #!/bin/bash # klaviyo-triage.sh -- run this first during any incident echo "=== Klaviyo Quick Triage ===" echo "Time: $(date -u +%Y-%m-%dT%H:%M:%SZ)" # 1. Is Klaviyo itself down? echo "" echo "--- Klaviyo Status Page ---" curl -s "https://status.klaviyo.com/api/v2/status.json" 2>/dev/null \ | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Status: {d[\"status\"][\"description\"]}')" \ || echo "Could not reach status page" # 2. Can we authenticate? echo "" echo "--- API Auth Check ---" HTTP_CODE=$(curl -s -w "%{http_code}" -o /tmp/klaviyo-triage.json \ -H "Authorization: Klaviyo-API-Key $KLAVIYO_PRIVATE_KEY" \ -H "revision: 2024-10-15" \ "https://a.klaviyo.com/api/accounts/" 2>/dev/null) echo "Auth response: HTTP $HTTP_CODE" # 3. Rate limit status echo "" echo "--- Rate Limit Headers ---" curl -s -I \ -H "Au...