Overview¶
The cluster-wide health landing page — an incident list, per-namespace health verdicts, active alerts and system health, with an optional embed of your own Grafana dashboard in its place.
Tier: Free
What it does¶
The Overview page is the landing view after login, and it is always cluster-wide:
it covers every namespace KubeManta is allowed to see, whatever the top-bar
namespace selector is set to. It shows a health verdict per namespace — critical,
degraded, healthy or unknown — derived from failing pods, Deployments below their
desired replica count, firing alerts, Pending pods and unbound PVCs; an incident
list that puts the worst problem first, described below; the active alert count
pulled from the Alerts rules engine; and a system health widget covering API
server latency and node-ready count, refreshed every 60 seconds in the
background. The incident list polls every 15 seconds; the namespace grid
refreshes when the Server-Sent Events stream signals that a fresh result exists,
and falls back to the same 15-second poll when that connection can't be
established. /overview is served from a 30-second server-side cache, so a
namespace verdict can be up to 30 seconds behind the cluster.
When a Grafana source is configured in Admin → Observability, one of your own dashboards can be embedded as the Overview instead of KubeManta's own cards — useful if you already have a curated cluster dashboard and want it to be the first thing an operator sees on login.
The namespace selector in the top bar scopes Workloads, Diagnose, Terminal and
Alerts to one namespace or all tenant namespaces at once; Overview is not among
them. What does change this page is the System NS toggle, a button in the
Overview header, which shows or hides the namespaces KubeManta treats as
system-owned so the page doesn't drown in infrastructure noise by default.
Setting it requires an admin, and it applies to everyone. That set is any
namespace whose name begins kube-, gke-, gmp-, istio- or knative-,
plus these exact names: kube-system, kube-public, kube-node-lease,
istio-system, cert-manager, ingress-nginx, monitoring, logging,
flux-system, argo, argocd, paas-core and kubemanta-system. Several of
those are ordinary names — if you run your own workloads in a namespace called
monitoring or logging, it stays hidden from Overview, Workloads and Alerts
until System NS is switched on.
Incidents¶
The top of the page is an incident list, not a metric. KubeManta derives a story per unhealthy pod from what it can already see — recent events, the log tail from the CRASHED instance rather than its healthy replacement, the exit code and reason, and the resource picture — and ranks them so the worst is first.
Clicking one opens the full story: what happened, in what order, with the evidence attached. For an admin the same view offers the remediation actions that fit the failure. Restart and Scale execute as soon as you click them, deleting a pod asks for an inline confirmation first, and all three are written to the audit log. The AI-recommended fix is the one that is approval-gated: applying it spends a single-use token issued with the plan, and a high-risk change also makes you type the target's name. A viewer sees the story without the buttons.
This ordering is deliberate. A dashboard that opens on totals asks you to notice the problem yourself; opening on the incidents puts the thing you would have gone looking for at the top of the page.
Setup¶
No configuration is required — Overview works out of the box against any cluster KubeManta can read. The optional Grafana embed is configured under Admin → Observability, alongside the Prometheus and Alertmanager connectors described on the Metrics and Alerts pages.
Troubleshooting¶
If a namespace is missing from Overview, check the namespace allowlist and the System NS toggle — the top-bar selector has no effect on this page. A namespace outside the allowlist, or one whose name KubeManta treats as system-owned, will simply not appear rather than show as unhealthy.
If the namespace grid stops moving while the incident list keeps updating, look
at the Server-Sent Events path, but note which direction the dependency runs:
the stream carries only a signal that a newer /overview result exists, and
that signal is emitted when the result is computed. Reloading the page fetches
one directly. A dropped EventSource connection is not the failure it looks like
— when the stream is unavailable the page polls /overview itself every 15
seconds.
Generated from KubeManta 1.2.0 — this page is rendered from the product's own documentation, so it cannot drift from what ships. Manifest built 2026-09-12T02:14:45Z.