KubeBolt docs
ENES GitHub

Core Concepts

Dashboard: Overview · Capacity · Reliability · Cost

The per-cluster dashboard follows a scan-then-dive rhythm — a summary layer that answers "is anything on fire?", with deep instrumentation below.

On this page
  1. The card row every tab opens with
  2. Overview — is everything fine right now?
  3. Capacity — a scan layer over the trends
  4. Reliability — golden signals, honest colors
  5. Shared behavior
  6. Cost (beta)

Each cluster’s dashboard is organized into 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. Open it with Dashboard in the top bar (its neighbour, Cluster Map, is the topology view). Overview and Capacity are always there; Reliability appears when the cluster ships Hubble flow data, and Cost (beta) when it ships OpenCost data. A tab with nothing to show is hidden rather than rendered empty.

Sub-tabQuestion it answersNeeds
OverviewIs everything fine right now?Nothing beyond a connection; Metrics Server for live usage
CapacityHow is the cluster consuming, and is it sized right?Metrics history from the agent for the card row and the trend charts
ReliabilityWhat is the cluster actually serving?Agent with Hubble enabled (Cilium); HTTP (L7) flows for the golden signals
Cost (beta)What does it cost, and what is idle?OpenCost data shipped by the agent; see Cost

Every tab opens with the same header: a breadcrumb (Clusters / cluster / tab), the cluster’s name, and a line with the tab’s purpose, the cloud provider and region (detected from node metadata; they simply don’t render when they can’t be determined), the Kubernetes version and the node and namespace counts. On Overview, a line under the tabs lists which data sources are shipping samples for this cluster (the agent, Hubble, node-exporter and so on), and on a metrics-only cluster (an agent that ships metrics but gives KubeBolt no API access) a banner says the metrics dashboards work while the live resource views and operations are off, and how to turn them on.

The card row every tab opens with

Overview, Capacity, Reliability and Cost each open with a row of four cards built the same way: a large figure, one sentence saying what it means right now, a small chart chosen for that metric, and a mono caption with the breakdown and links to the lists behind it.

Overview — is everything fine right now?

Overview has no range selector: everything on it is current state, and the trends live in Capacity. Its four cards:

CardShowsLights up
Cluster healthThe score out of 100 on a half gauge, with a Healthy, Warning or Critical chip. The score adds up four checks (API server reachable, 25; nodes Ready, up to 25; Metrics Server available, 10; pods not failed or crash-looping, up to 40), then takes off 5 points per open critical insight (at most 25) and 2 per warning (at most 10). An open critical makes the chip Critical whatever the score. The card lists what took points off, and hovering shows every checkNever: the Insights card beside it carries the alert. Out of contact with the cluster it shows no score and a grey No contact chip
Nodes readyReady nodes over the total, and the three busiest (by the higher of CPU and memory) as double rings (CPU inside, memory outside) with “+N more”. Without node metrics, a Ready / Not ready listRed when a node is not ready, amber when one is cordoned
PodsRunning pods over the active ones, and the pod count over the last 24 hours as a line (needs the agent; without it, a Running / Degraded list). The caption splits completed · degraded · not running, each linking to its filtered listRed when pods are not running, amber when they are degraded (Pending, CrashLoopBackOff, partially ready)
InsightsOpen insights as cases (one per rule and object; pods of one workload fold together), worst and oldest first, up to three rows; a rule with three or more cases becomes one row, rule ×N. The caption splits critical · warning · infoRed with a critical open, amber with a warning

Completed Job pods are left out of the pods denominator, so a batch of finished Jobs never reads as missing pods. Muted insights are left out of the Insights card and the health score; a critical one still counts.

Below the cards:

The Overview tab: efficiency, workload health and what needs attention, on one screen.
The Overview tab: efficiency, workload health and what needs attention, on one screen. KubeBolt 2.1.1

The card row and the trend charts read metrics history, so they need the agent; without it the trends block shows a placeholder and the card row is not drawn.

Capacity: requests against real usage, per node and per workload.
Capacity: requests against real usage, per node and per workload. KubeBolt 2.1.1

Reliability — golden signals, honest colors

Reliability: the golden signals, with colors that only turn when something is actually wrong.
Reliability: the golden signals, with colors that only turn when something is actually wrong. KubeBolt 2.1.1

The Reliability tab is powered by Hubble flow data, so it appears only on agent-connected clusters with Hubble enabled (hubble.enabled=true on the agent chart). The golden signals need HTTP (L7) flows: when Hubble ships only L3/L4 flows (Cilium running without its L7 proxy, as on GKE’s managed Dataplane V2) the tab explains that instead of drawing empty panels, and those flows still feed the Cluster Map’s Traffic layout. See Connecting clusters.

Shared behavior

The selected time range (5 minutes to 30 days) is shared between Capacity, Reliability and Cost and persists while you drill into resources, but resets to the 15-minute default on a fresh browser session, so the daily scan never accidentally fires a 30-day query. The Monitor tab of each resource keeps a range of its own.

Cost (beta)

Spend, idle cost, cost per pod and money-priced rightsizing, from OpenCost data the agent ships. It is covered on its own page: Cost.