Skip to main content
GET
Get Incident Timeline
string
required
Name of the Issue resource (e.g., payment-service-oom-kill-1773933600)
string
Only look for the PostMortem in this namespace. When omitted, every namespace is searched.
The timeline is read from the PostMortem whose issueRef is this incident (status.timeline). A PostMortem is generated when a RemediationPlan of the incident finishes (resolved or contained), so an incident that is still being analyzed or remediated, was escalated without a finished plan, or was resolved manually has no timeline yet and returns 404. Event type values written by the operator are detected, action_executed, action_failed and resolved; in agentic mode each step becomes one event whose detail includes the AI reasoning. The list is not paginated (page is always 1).

Authorizations

X-API-Key
string
header
required

API key sent in the X-API-Key header. Keys are read from the Secret chatcli-operator-secrets, key api-keys (fallback: ConfigMap chatcli-operator-config, key api-keys) in the operator namespace, as a YAML list of {key, role, name, description} (name is the identity recorded on approval decisions); the operator chart creates it only with apiKeys.create: true. Roles: viewer < operator < admin — any other role string is denied everywhere. Changes are picked up within about 30 seconds; deleting both the Secret and the ConfigMap revokes every key. With no keys configured every /api/ call returns 401, unless CHATCLI_OPERATOR_DEV_MODE=true, which grants admin without a key (development only).

Path Parameters

name
string
required

Issue name.

Example:

"payment-service-oom-1710860400"

Query Parameters

namespace
string

Kubernetes namespace. Empty means all namespaces.

Response

Timeline events

apiVersion
string
Example:

"v1"

kind
string
Example:

"IncidentTimeline"

metadata
object
items
object[]