# Monitor the fleet and the server (admin)

> For administrators: a daily routine for seeing blockers, datasheet and enrichment gaps, stale stamps and server status.

_Source: E-Sharp (esharp.se) · Probe guide_


*This page is for the administrator.*

The fleet and system views give you a daily overview. Here's a simple routine.

## The fleet

- **Overview and blockers per owner** — which boards are stuck and on what.
- **Datasheet and enrichment gaps** — where the corpus lacks what it needs (see [the datasheet corpus lifecycle](/en/probe/support/datasheet-corpus-lifecycle)).
- **Stale protocol stamps** — boards whose classification has gone old.

## The server

- **Version, licence and change log** — what's running and what the licence allows (see [seats, licence and fleet](/en/probe/support/seats-licence-and-fleet)).
- **Read audit** — who has read what (see [change log and audit](/en/probe/support/change-log-and-audit)).

## A daily routine

Look at blockers per owner, close the datasheet gaps you can, and keep an eye on runs that have stalled (see [background jobs and walkers](/en/probe/support/background-jobs-and-walkers)). Five minutes is enough to keep the fleet moving.

---

*Probe is E-Sharp's design-review engine.*
