better-stack-incidents

# Better Stack Incidents ## Overview Incidents in Better Stack are triggered automatically when uptime monitors detect downtime, or created manually for ad-hoc issues. Each incident tracks the timeline from detection through acknowledgment to resolution, with associated monitors, status page updates, and on-call notifications. ## Key Concepts ### Incident Lifecycle 1. **Triggered** - Monitor detects downtime and creates an incident 2. **Acknowledged** - On-call responder acknowledges the incident 3. **Resolved** - The issue is fixed and the incident is closed 4. **Auto-resolved** - Monitor detects recovery and automatically resolves ### Incident Attributes - **Started at** - When the incident was first detected - **Acknowledged at** - When a responder acknowledged - **Resolved at** - When the incident was resolved - **Cause** - The monitor or manual source that triggered it - **Call** - Whether a phone call alert was triggered - **SMS** - Whether an SMS alert was sent - **Email** - Whether an email alert was sent ### Incident Severity Better Stack does not enforce severity levels on incidents directly -- severity is determined by the monitor's configuration and escalation policy. However, incidents from monitors with shorter check intervals and immediate escalation are implicitly higher priority. ## API Patterns ### List Incidents ``` betterstack_list_incidents ``` Parameters: - `page` - Pagination cursor - `per_page` - Results per page - `from` - Start date filt...