Skip to main content
GET
Analytics MTTR
string
Start of the window, RFC 3339 (e.g., 2026-03-01T00:00:00Z). An unparseable value is ignored.
string
End of the window, RFC 3339.
Minimum role: viewer. Covers every namespace. There are no period, severity, namespace or granularity parameters, and no percentile, per-severity or per-phase breakdown. Only Issues in state Resolved with status.resolvedAt set are counted; Issues induced by a chaos experiment (label platform.chatcli.io/source: chaos-experiment) are left out. The resolution time is resolvedAt − creationTimestamp, grouped by the day the Issue was created (YYYY-MM-DD, ascending). In each item, value is the mean in seconds and count the number of Issues that day.

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

Query Parameters

from
string<date-time>

Start of the time range (RFC3339). Unparseable values are ignored.

Example:

"2026-03-01T00:00:00Z"

to
string<date-time>

End of the time range (RFC3339). Unparseable values are ignored.

Example:

"2026-03-19T23:59:59Z"

Response

MTTR per day

apiVersion
string
Example:

"v1"

kind
string
Example:

"MTTRMetrics"

metadata
object
items
object[]