Skip to main content
GET
Analytics MTTD
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. For each Issue created in the window, except Issues induced by a chaos experiment (label platform.chatcli.io/source: chaos-experiment), the detection time is status.detectedAt − metadata.creationTimestamp (0 when detectedAt is empty or earlier). Issues are grouped by the day they were created (YYYY-MM-DD, ascending). In each item, value is the mean in seconds and count the number of Issues that day. Because an Issue is created when the operator reacts to an anomaly, this measures the gap between the Issue and its detection mark, not the time from the underlying fault to detection. Values near 0 are expected.

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

MTTD per day

apiVersion
string
Example:

"v1"

kind
string
Example:

"MTTDMetrics"

metadata
object
items
object[]