documenso-incident-runbook

# Documenso Incident Runbook ## Overview Step-by-step procedures for responding to Documenso integration incidents. Covers cloud outages, self-hosted issues, and integration failures. ## Prerequisites - Access to monitoring dashboards - Documenso dashboard access - Application log access - On-call escalation contacts defined ## Severity Levels | Level | Description | Examples | Response Time | |-------|-------------|----------|---------------| | P1 | Complete signing outage | All API calls failing, no documents can be sent | < 15 min | | P2 | Degraded functionality | Slow responses, intermittent errors, webhooks delayed | < 1 hour | | P3 | Minor issue, workaround available | Single document stuck, UI glitch | < 4 hours | | P4 | Non-urgent | Feature request, documentation gap | Next business day | ## Quick Diagnostic Commands ```bash #!/bin/bash set -euo pipefail echo "=== Documenso Incident Diagnostic ===" # 1. Check Documenso cloud status echo "--- Cloud Status ---" curl -s https://status.documenso.com/api/v2/status.json 2>/dev/null | jq '.status' || echo "Status page unreachable" # 2. Check our API connectivity echo "--- API Connectivity ---" BASE="${DOCUMENSO_BASE_URL:-https://app.documenso.com/api/v1}" HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" \ -H "Authorization: Bearer $DOCUMENSO_API_KEY" \ "$BASE/documents?page=1&perPage=1" 2>/dev/null || echo "000") echo "API Status: $HTTP_CODE" # 3. Check latency (5 samples) echo "--- Latency Check ---" for i ...