miro-incident-runbook

# Miro Incident Runbook ## Overview Rapid incident response for Miro REST API v2 integration failures: triage, mitigation, recovery, and postmortem. ## Severity Levels | Level | Definition | Response | Example | |-------|------------|----------|---------| | P1 | Complete integration outage | < 15 min | Miro API returns 5xx on all calls | | P2 | Degraded service | < 1 hour | High latency, partial 429s | | P3 | Minor impact | < 4 hours | Webhook delays, single-board errors | | P4 | No user impact | Next business day | Monitoring gaps, non-critical warnings | ## Quick Triage (First 5 Minutes) ```bash #!/bin/bash # miro-triage.sh — Run this first during any Miro incident echo "=== MIRO TRIAGE $(date -u +%H:%M:%SZ) ===" # 1. Is Miro itself down? echo -n "Miro Status: " curl -sf "https://status.miro.com/api/v2/status.json" | jq -r '.status.description' 2>/dev/null || echo "STATUS PAGE UNREACHABLE" # 2. Can we reach the API? echo -n "API Connectivity: " curl -s -o /dev/null -w "HTTP %{http_code} (%{time_total}s)" \ -H "Authorization: Bearer ${MIRO_ACCESS_TOKEN}" \ "https://api.miro.com/v2/boards?limit=1" 2>/dev/null echo "" # 3. What's our rate limit status? echo "Rate Limit:" curl -sI -H "Authorization: Bearer ${MIRO_ACCESS_TOKEN}" \ "https://api.miro.com/v2/boards?limit=1" 2>/dev/null | \ grep -i "x-ratelimit\|retry-after" || echo " No rate limit headers" # 4. Token validity echo -n "Token: " TOKEN_RESP=$(curl -s -H "Authorization: Bearer ${MIRO_ACCESS_TOKEN}" ...