| name | gamma-incident-runbook |
| description | Manage incident response for Gamma integration issues.
Use when experiencing production incidents, outages,
or need systematic troubleshooting procedures.
Trigger with phrases like "gamma incident", "gamma outage",
"gamma down", "gamma emergency", "gamma runbook".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*), Grep |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","gamma","incident-response"] |
| compatibility | Designed for Claude Code |
Gamma Incident Runbook
Overview
Systematic procedures for responding to and resolving Gamma integration incidents.
Prerequisites
- Access to monitoring dashboards
- Access to application logs
- On-call responsibilities defined
- Communication channels established
Incident Severity Levels
| Level | Description | Response Time | Escalation |
|---|
| P1 | Complete outage, no presentations | < 15 min | Immediate |
| P2 | Degraded, slow or partial failures | < 30 min | 1 hour |
| P3 | Minor issues, workaround available | < 2 hours | 4 hours |
| P4 | Cosmetic or non-urgent | < 24 hours | None |
Quick Diagnostics
Step 1: Check Gamma Status
set -euo pipefail
curl -s https://status.gamma.app/api/v2/status.json | jq '.status'
curl -s https://your-app.com/health/gamma | jq '.'
curl -w "\nTime: %{time_total}s\n" \
-H "Authorization: Bearer $GAMMA_API_KEY" \
https://api.gamma.app/v1/ping
Step 2: Review Key Metrics
set -euo pipefail
curl -s 'http://prometheus:9090/api/v1/query?query=rate(gamma_requests_total{status=~"5.."}[5m])' | jq '.data.result'
curl -s 'http://prometheus:9090/api/v1/query?query=histogram_quantile(0.95,rate(gamma_request_duration_seconds_bucket[5m]))' | jq '.data.result'
curl -s 'http://prometheus:9090/api/v1/query?query=gamma_rate_limit_remaining' | jq
