> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# incidents

> DevHelm CLI incidents commands — list, get, create, and resolve incidents

View and manage incidents from the command line. List active incidents, inspect details, create manual incidents, and resolve them.

## Commands

| Command | Description |
| - | - |
| `devhelm incidents list` | List incidents |
| `devhelm incidents get <id>` | Get incident details |
| `devhelm incidents create` | Create a manual incident |
| `devhelm incidents resolve <id>` | Resolve an incident |

## incidents list

List all incidents in your organization.

```bash theme={null}
devhelm incidents list
```

| Flag | Type | Default | Description |
| - | - | - | - |
| `--page-size` | integer | `200` | Number of items per API request (1–200) |

Incident `status` is one of `WATCHING`, `TRIGGERED`, `CONFIRMED`, or `RESOLVED`. Filter with `jq` — for example, everything that isn't resolved yet:

```bash theme={null}
devhelm incidents list -o json | jq '[.[] | select(.status != "RESOLVED")]'
```

## incidents get

Get detailed information about a single incident, including its timeline. Incident IDs are UUIDs — get them from `devhelm incidents list`.

```bash theme={null}
devhelm incidents get <incident-id>
```

```bash theme={null}
devhelm incidents get <incident-id> -o json
```

## incidents create

Create a manual incident. Manual incidents are useful for tracking outages detected outside of automated monitoring.

```bash theme={null}
devhelm incidents create \
  --title "Payment API degraded" \
  --severity DEGRADED
```

| Flag | Type | Required | Description |
| - | - | - | - |
| `--title` | string | Yes | Short summary of the incident |
| `--severity` | string | Yes | Severity: `DOWN`, `DEGRADED`, `MAINTENANCE` |
| `--monitor-id` | string | — | Associate with a specific monitor (UUID) |
| `--body` | string | — | Detailed description of the incident |

### Examples

```bash theme={null}
devhelm incidents create \
  --title "Scheduled database migration" \
  --severity MAINTENANCE \
  --body "Migrating to new schema, expected 10min downtime"
```

```bash theme={null}
devhelm incidents create \
  --title "CDN provider outage" \
  --severity DOWN \
  --monitor-id <monitor-id>
```

## incidents resolve

Resolve an active incident.

```bash theme={null}
devhelm incidents resolve <incident-id>
```

Add a resolution message:

```bash theme={null}
devhelm incidents resolve <incident-id> --message "Root cause identified and patched"
```

| Flag | Type | Description |
| - | - | - |
| `--message` | string | Resolution message added to the incident timeline |

## Next steps

<CardGroup cols={2}>
  <Card title="Incidents overview" icon="triangle-exclamation" href="/incidents/overview">
    Understanding incident lifecycle and policies.
  </Card>

  <Card title="Manual incidents guide" icon="wrench" href="/guides/manual-incident-management">
    Step-by-step guide for managing manual incidents.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.