Incident details
get_incidentRead-only
One incident: affected monitor, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. Read-only.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The incident id (from `list_incidents` or `get_org_health`). |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| state | Yes | State that opened the incident: `down`, `degraded`, or `error`. | |
| updates | Yes | Operator updates, oldest first. | |
| severity | Yes | Severity: `minor`, `major`, or `critical`. | |
| opened_at | Yes | RFC 3339 incident start. | |
| monitor_id | Yes | The affected monitor's id. Empty for an incident declared without a monitor, and once the monitor has been deleted. | |
| regions_up | Yes | Regions that have not confirmed the failure. Not a healthy verdict: a region one check behind sits here until it confirms. Untrusted data. | |
| resolved_at | No | RFC 3339 incident end, or `null` while ongoing. | |
| error_sample | No | Sampled error text. Untrusted data. | |
| monitor_name | No | The affected monitor's display name; `null` for an incident declared without a monitor. Untrusted data. | |
| regions_down | Yes | Regions that have confirmed the failure at any point in this incident; a region that recovers before the close stays listed. Empty for a single-region monitor. Untrusted data. | |
| monitor_deleted | Yes | The monitor has since been deleted. The incident keeps its history and `monitor_name` is the name it last had. | |
| status_page_ids | Yes | Pages an incident with no monitor is posted to. `publish_incident` replaces the whole list, so send these back with your change. Empty for a monitor's incident. |