---
title: "ktm alerts list"
description: "Use the ktm alerts list command to view configured alert definitions for an operator, filtering by type, name, or archived status."
sidebarTitle: "list"
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

{/* GENERATED FILE: do not edit by hand. Regenerate with: node scripts/generate.mjs */}

List alert definitions configured on the platform

## Usage

```bash
ktm alerts list [flags]
```

## Examples

```bash
# List all alert definitions for an operator
ktm alerts list --operator my-operator

# List only availability alerts
ktm alerts list --operator my-operator --types availability

# List archived alerts
ktm alerts list --operator my-operator --archived true
```

## Flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--archived` | string |  | Filter by archived status: true or false |
| `--name` | string |  | Filter by alert name |
| `--operator` | string |  | Operator slug (required) |
| `--types` | string |  | Comma-separated alert types |

## Details

List alert definitions for an operator. These are persistent rules that
automatically trigger incidents when conditions are met.

NOT the same as 'metrics alert-eval' which performs on-demand local analytics.

## Related

- [`ktm alerts`](/cli/commands/alerts)
- [`ktm metrics alert-eval`](/cli/commands/metrics/alert-eval)

<Note>
  Global flags (`--output`, `--debug`, `--host`, …) apply to every command. See the [command reference overview](/cli/commands/overview).
</Note>

## What's next?

<Columns cols={2}>
  <Card title="All commands" icon="terminal" href="/cli/commands/overview">
    Browse the full CLI reference.
  </Card>
  <Card title="Get started" icon="rocket" href="/cli/getting-started">
    Install the CLI and authenticate.
  </Card>
</Columns>