maintainx-incident-runbook

# MaintainX Incident Runbook ## Overview Step-by-step procedures for responding to MaintainX integration incidents, from detection through resolution and post-mortem. ## Prerequisites - Access to monitoring dashboards - MaintainX admin API credentials - On-call contact list ## Severity Classification | Severity | Definition | Response Time | |----------|-----------|---------------| | **SEV-1** | Complete integration failure, no work orders processing | 15 min | | **SEV-2** | Partial failure, some endpoints degraded | 1 hour | | **SEV-3** | Performance degradation, slow responses | 4 hours | | **SEV-4** | Non-critical feature broken, workaround available | Next business day | ## Instructions ### Step 1: Immediate Triage (First 5 Minutes) ```bash #!/bin/bash echo "=== MaintainX Incident Triage ===" echo "Time: $(date -u)" # Check MaintainX API status echo -e "\n--- API Health ---" for endpoint in users workorders assets locations; do CODE=$(curl -s -o /dev/null -w "%{http_code}" \ "https://api.getmaintainx.com/v1/$endpoint?limit=1" \ -H "Authorization: Bearer $MAINTAINX_API_KEY") echo " /$endpoint: HTTP $CODE" done # Check your integration service echo -e "\n--- Integration Service ---" curl -s http://localhost:3000/health | jq . 2>/dev/null || echo " Service unreachable" # Check recent error logs echo -e "\n--- Recent Errors (last 10 min) ---" # Adjust for your log system: # journalctl -u maintainx-sync --since "10 min ago" --no-pager | grep -i error | ...