> ## 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.

# status-data

> DevHelm CLI status-data commands — browse the service catalog and manage dependencies

Interact with Status Data from the command line. Browse third-party services from the catalog, check their status, view uptime history and incidents, and manage your tracked dependencies.

## Commands

The status-data surface spans two command groups:

### Service catalog

| Command                                           | Description                                          |
| ------------------------------------------------- | ---------------------------------------------------- |
| `devhelm services list`                           | Browse the service catalog                           |
| `devhelm services get <slug>`                     | Get full detail for a service                        |
| `devhelm services status <slug>`                  | Lightweight live-status snapshot                     |
| `devhelm services summary`                        | Global status summary across the whole catalog       |
| `devhelm services components <slug>`              | List a service's components                          |
| `devhelm services categories`                     | List categories with service counts                  |
| `devhelm services uptime <slug>`                  | View uptime history for a service or component       |
| `devhelm services incidents [slug] [incident-id]` | List incidents, or show one incident's full timeline |
| `devhelm services maintenances <slug>`            | List scheduled maintenances                          |

### Dependencies

| Command                             | Description                    |
| ----------------------------------- | ------------------------------ |
| `devhelm dependencies list`         | List your tracked dependencies |
| `devhelm dependencies get <id>`     | Get dependency details         |
| `devhelm dependencies track <slug>` | Add a service as a dependency  |
| `devhelm dependencies update <id>`  | Change alert sensitivity       |
| `devhelm dependencies delete <id>`  | Remove a dependency            |

## services list

Browse the catalog. Cursor-paginated.

```bash theme={null}
devhelm services list
devhelm services list --search stripe
devhelm services list --category cloud-infrastructure
```

| Flag         | Type   | Default | Description                                    |
| ------------ | ------ | ------- | ---------------------------------------------- |
| `--search`   | string | —       | Case-insensitive match on service name or slug |
| `--category` | string | —       | Filter by category (exact match)               |
| `--status`   | string | —       | Filter by current overall status               |
| `--limit`    | int    | `20`    | Page size (1–100)                              |
| `--cursor`   | string | —       | Opaque cursor from a previous response         |

## services get

Get the full service profile: current status, components, recent incidents, uptime summary.

```bash theme={null}
devhelm services get github
devhelm services get stripe -o json
```

## services status

Lightweight live-status snapshot — current overall status, component statuses, and active incident count. Ideal for polling.

```bash theme={null}
devhelm services status github
```

## services summary

Global status summary: counts of operational / degraded / down services across the entire catalog, with the list of currently affected services.

```bash theme={null}
devhelm services summary
```

## services components

List a service's components with current status. Use this to find component IDs for component-level dependencies.

```bash theme={null}
devhelm services components github
```

## services categories

```bash theme={null}
devhelm services categories
```

## services uptime

View uptime history for a catalog service, or for a single component with `--component`.

```bash theme={null}
devhelm services uptime aws-ec2
devhelm services uptime aws-ec2 --period 90d --granularity daily
devhelm services uptime github --component <component-id> --period 30d
```

| Flag              | Type   | Default | Description                                                 |
| ----------------- | ------ | ------- | ----------------------------------------------------------- |
| `--period`        | string | `30d`   | Time period: `7d`, `30d`, `90d`                             |
| `--granularity`   | string | —       | Data granularity: `hourly`, `daily` (service-level only)    |
| `--component`     | UUID   | —       | Show uptime for this component instead of the whole service |
| `--from` / `--to` | string | —       | Custom ISO 8601 date range (requires `--component`)         |

Find component IDs with `devhelm services components <slug>`.

## services incidents

List vendor incidents, or show one incident in full. With a slug, lists that service's incident history; without, lists incidents across all services. Add an incident ID after the slug to see the complete vendor timeline for a single incident.

```bash theme={null}
devhelm services incidents github --status active
devhelm services incidents --status active
devhelm services incidents github <incident-id>
```

| Flag       | Type   | Default | Description                    |
| ---------- | ------ | ------- | ------------------------------ |
| `--status` | string | —       | `active` or `resolved`         |
| `--from`   | string | —       | Earliest start date (ISO 8601) |

## services maintenances

List scheduled maintenance windows announced by the vendor.

```bash theme={null}
devhelm services maintenances github
```

<Note>
  `devhelm data services status` and `devhelm data services uptime` from earlier CLI versions keep working as aliases of `services status` and `services uptime`.
</Note>

## dependencies list

List all services you're tracking as dependencies.

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

## dependencies get

```bash theme={null}
devhelm dependencies get <subscription-id> -o json
```

## dependencies track

Add a service from the catalog as a dependency. Once tracked, DevHelm monitors its status and routes incidents through your [notification policies](/alerting/notification-policies).

```bash theme={null}
devhelm dependencies track github
devhelm dependencies track stripe --alert-sensitivity INCIDENTS_ONLY
devhelm dependencies track github --component <component-id>
```

| Flag                  | Type   | Default     | Description                                            |
| --------------------- | ------ | ----------- | ------------------------------------------------------ |
| `--alert-sensitivity` | string | `AWARENESS` | `AWARENESS`, `INCIDENTS_ONLY`, `MAJOR_ONLY`, or `ALL`  |
| `--component`         | UUID   | —           | Track only this component instead of the whole service |

## dependencies update

Change alert sensitivity for an existing dependency.

```bash theme={null}
devhelm dependencies update <subscription-id> --alert-sensitivity MAJOR_ONLY
```

## dependencies delete

Stop tracking a service.

```bash theme={null}
devhelm dependencies delete <subscription-id>
```

## Next steps

<CardGroup cols={2}>
  <Card title="Status Data overview" icon="globe" href="/status-data/overview">
    Understanding the service catalog and dependency tracking.
  </Card>

  <Card title="Tracking dependencies guide" icon="wrench" href="/guides/tracking-dependencies">
    Step-by-step guide for adding third-party dependencies.
  </Card>
</CardGroup>