ktm incidents list

List incidents (triggered alerts) on the platform

Usage

ktm incidents list [flags]

Examples

# List open incidents
ktm incidents list --operator my-operator --status OPEN

# List incidents for a specific alert
ktm incidents list --operator my-operator --alert-id 42

# List incidents created after a date
ktm incidents list --operator my-operator --created-after 2026-03-01T00:00:00Z

Flags

Flag	Type	Default	Description
`--alert-id`	string		Comma-separated alert definition IDs
`--closed-after`	string		Filter incidents closed after this ISO datetime
`--closed-before`	string		Filter incidents closed before this ISO datetime
`--created-after`	string		Filter incidents created after this ISO datetime
`--created-before`	string		Filter incidents created before this ISO datetime
`--operator`	string		Operator slug (required)
`--page`	int	`1`	Page number
`--page-size`	int	`50`	Results per page
`--status`	string		Filter by status: OPEN, CLOSED, MANUALLY_CLOSED, CHANGED, DEACTIVATED

Details

List incidents for an operator. Incidents are created when a platform alert definition fires. They track the lifecycle from OPEN to CLOSED.

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

Global flags (--output, --debug, --host, …) apply to every command. See the command reference overview.

What's next?

All commands

Browse the full CLI reference.

Get started

Install the CLI and authenticate.