Dashboard: Overview · Capacity · Reliability

Each cluster’s dashboard is organized into three sub-tabs built around a scan → dive rhythm: a summary layer up top answers the urgent question at a glance, and the detailed panels below let you drill into anything. Every summary number is derived from metrics already shown in the panels beneath it — no extra data sources to configure.

Overview — efficiency as the hero

• Resource efficiency band — a capacity axis per resource with three stripes: used, requested-but-idle (striped), and free. The reclaimable gap is drawn explicitly, with per-resource efficiency scores and right-size callouts where there’s something to reclaim.
• Identity header — breadcrumb plus the cluster’s cloud provider and region, detected automatically from node metadata (they simply don’t render when undeterminable — nothing to configure).
• Workload health at a glance. Completed Job pods are counted apart from Running, so terminal pods don’t inflate the health ring.

Capacity — a scan layer over the trends

• Summary strip: peak CPU / memory (with sparklines), a rightsizing opportunity aggregate, and OOMKills in the selected range.
• Recent Deploys and Recent OOMKills as scannable tables. OOMKills are enriched with the container’s memory limit and restart count — you can tell a chronic crash loop from a one-off — and each row has an Ask Kobi affordance to investigate.
• Right-sizing rows show per-item reclaimable CPU and memory. With cost data connected, the Cost tab prices those same recommendations.

Reliability — golden signals, honest colors

• Golden-signals strip: error rate (5xx), latency, throughput, and L4 drops, each with a delta against the previous window of the same length.
• Class-pinned colors: 5xx is always red and 4xx always amber, even when one class has no data in range.
• Latency is labeled as an average — the agent ships sum + count, not histogram buckets — and a tooltip says so instead of letting you assume a p99.

Shared behavior

The selected time range is shared between Capacity and Reliability and persists while you drill into resources, but resets to the 15-minute default on a fresh session — the daily scan never accidentally fires a 30-day query.