Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 1 hour▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 12:35:56.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← system alerts

k8s_events

What the cluster itself reports going wrong, from its events (every namespace): pods that cannot start for 10+ minutes (image pull, config error, unschedulable), evictions, kernel OOM kills (including a process inside a running container), Jobs out of retries, ExternalSecrets not syncing, cert-manager or other platform pods down, autoscalers that cannot read their metric, and node problems. Judged on the current state: still being reported, and a normal wait (a pod pending two minutes, then scheduled) is not an incident.
opens pod.cannot_start, pod.evicted, pod.oom, job.backoff, secret.sync_failing, cert.unhealthy, platform.unhealthy, scaler.failing, node.unhealthy · once per cluster · shipped cadence every 5 min

Its settings — the system default is shown beside each; ↺ puts one back

This detector has no tunable settings — its behaviour is entirely its logic.