Skip to main content
Here’s what each screen is for: Overview and Fleet Map cover the whole fleet (and every cluster, in a multi-cluster setup); the other screens focus on one engine, chosen with the filter in the page header.

​
Overview

The landing page: overall fleet health, per-engine cards, and two lists that name what needs attention. Each entry links straight to the affected node.
  • Alerts — facts your cluster is reporting: an engine not fully ready, a failing health check (with the failing nodes named), a storage backend down.
  • Issues — your thresholds applied to live values, each naming the worst offender.

​
Fleet Map

Every engine, node, and GPU in one view. Pick a lens (Health, Utilization, or Capacity) and the whole map colors by it, so the affected node stands out. Selecting a node shows its key numbers, its GPUs (when GPU telemetry is connected), and its recent trends. Nodes can be nicknamed, for example by the model they serve.

​
Metrics

The trends for one engine, with your warn/critical bands drawn on every chart:

​
Health

What’s happening inside the engine: health tiles, the cache pipeline, and the event log. Issues & Fixes turns anything failing into a problem card with a suggested fix that matches the cause (a storage-backend failure points at the backend, not “restart the pod”). Health here is the engine’s own self-assessment, not just pod status, so it catches problems standard Kubernetes tooling can’t see, like a storage connection silently disabled after repeated failures while the pod still looks fine.

​
Thresholds

Where you decide what counts as degraded vs. critical: driving the colors, the Issues list, and notifications. Covered in Thresholds & Notifications.