# Monitor a fleet

Source: [https://docs.aventail.co.uk/docs/fleet/dashboard](https://docs.aventail.co.uk/docs/fleet/dashboard)

Open **Fleet operations → Devices** in the intended organisation.

### Check fleet readiness

Development Control, 2 October 2026. Keys and identifying details are obscured.

1.  **Inspect reachability and revision**
    
    Use the filters to find a device. Compare its online state, agent version and configuration, then open it for model and routing details.
    
    [Screenshot: Device status and filters — close-up from Fleet device monitoring.](https://docs.aventail.co.uk/img/guides/context/fleet-devices.png)
    

**Read the monitoring and retirement guide**

## Read fleet health

| Indicator | What to check |
| --- | --- |
| Capacity | Enrolled devices against the organisation's limit |
| Reachability | Which devices have checked in recently |
| Agent compliance | Installed versions against the target version |
| Config rollout | How many devices report the intended revision |
| Telemetry freshness | The age of the latest reported data |

A recent status report does not prove a model can answer requests. Use a small inference test when confirming readiness.

## Inspect a device

Find the device and open its row. Check its identity, agent version, last-seen time and model status. The drawer also shows its tags, routing policy and effective route.

Compare **desired** and **applied** configuration revisions. If they differ, inspect deployment progress, connection state and recent activity before sending another change. After an offline device reconnects, verify convergence rather than assuming it caught up.

## Retire a device

Retirement removes the device from fleet management. Check the device ID, finish active work and arrange removal of local data separately.

Open the device drawer, choose **Retire device**, read the confirmation and proceed only for the intended device. Check the fleet list and capacity afterward.

An offline device cannot be assumed to have erased its files because its fleet record was removed. Follow your organisation's device-disposal procedure.