Health Monitoring
The agent reports the health of the robot and the host it runs on, so you can see problems in the fleet manager.
What the agent reports
- System health of the host — resource usage such as CPU, memory, and disk.
- Robot status and telemetry — the robot's operating mode and live status, derived from the data the agent ingests locally (see Telemetry).
These are published to the cloud over the agent's secure (mTLS) link and shown in the web app. A detailed reference of the exact health metrics and reporting intervals is coming soon.
How faults appear
When your robot software emits a fault, the agent ingests it from local Zenoh and forwards it uplink. Faults then surface in the fleet manager, where operators can see:
- That a robot has an active fault.
- Which robot and what kind of fault it is.
This lets operators triage issues across the fleet without logging into individual robots. For the fault message shape, see Health & status messaging.
Events
In addition to faults, the agent forwards events (notable occurrences reported by the robot). Like faults, these are ingested locally and published to the cloud so they appear in the fleet view.
Checking health on the robot
To inspect the agent locally, use the systemd service and its logs:
sudo systemctl status rover-agent
journalctl -u rover-agent -f # follow logs
If health or status is missing in the web app, confirm the agent is running, enrolled, and able to reach the cloud. See Verify agent connectivity.