> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensormesh.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring Your Fleet

> Overview, Fleet Map, Metrics, Health, and Thresholds — what each screen shows and when to use it.

Here's what each screen is for:

| Screen         | What it's for                                                       |
| -------------- | ------------------------------------------------------------------- |
| **Overview**   | The landing page — what needs attention right now                   |
| **Fleet Map**  | Drill down from engines to nodes to individual GPUs                 |
| **Metrics**    | Trends over time — utilization, cache fill, activity, quotas        |
| **Health**     | Inside the engine — the cache pipeline, events, and suggested fixes |
| **Thresholds** | Decide what counts as a problem                                     |

Overview and Fleet Map cover the whole fleet (and every cluster, in a
[multi-cluster](/operator/ui/configuration#multiple-clusters) 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](/operator/ui/thresholds-and-notifications) applied to live
  values, each naming the worst offender.

***

## Fleet Map

Every engine, node, and GPU in one place. Pick a lens — **Health**, **Utilization**, or
**Capacity** — and the whole map colors by it, so the problem node is visible at a glance.
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:

| Tab                | What it shows                                                       |
| ------------------ | ------------------------------------------------------------------- |
| **Serving**        | GPU and CPU utilization per node, per-node cache hit rate           |
| **Cache Capacity** | How full each cache tier is, and how fast entries are being evicted |
| **Cache Activity** | Cache reads vs. writes, traffic to and from secondary storage       |
| **Quotas**         | Each workload's cache budget and usage                              |

***

## 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 — and the
fix matches the cause (a storage-backend failure points at the backend, not "restart the
pod").

<Note>
  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.
</Note>

***

## Thresholds

Where you decide what counts as degraded vs. critical — driving the colors, the Issues list,
and notifications. Covered in
[Thresholds & Notifications](/operator/ui/thresholds-and-notifications).

***

## Related

* [Thresholds & Notifications](/operator/ui/thresholds-and-notifications)
* [Multi-Tenancy](/operator/management/multi-tenancy)
* [Troubleshooting & FAQ](/operator/ui/troubleshooting)
* [CLI Reference](/operator/reference/cli)