Fleet
Fleet analytics
Use /app/fleet/analytics to compare robot availability, mission outcomes, and active alerts for the whole workspace or a shareable cohort or tag selection.
On this page
Start here
Fleet analytics gives an operator a quick health snapshot for the whole workspace or a cohort or tag selection. Use it to spot changes in online utilization, mission outcomes, and active alerts, then follow the related fleet or mission screens for investigation.
Before you begin
- A signed-in workspace operator with access to /app/fleet/analytics
- Robots, missions, or alerts plus any consistently defined cohort or tag
Put it into practice
-
Set the operating slice
Open the analytics screen and choose a cohort or tag when you need a site, customer, or other fleet segment instead of workspace-wide totals.
-
Read denominators carefully
Compare online count with total robots for utilization, and remember that mission success divides completed by completed plus failed plus cancelled missions.
-
Share and investigate
Copy the filtered URL to preserve the view, then open fleet, mission, or alert detail to explain an unexpected aggregate.
The visible totals match the selected fleet slice, another operator can open the same filtered URL, and unusual values lead to a concrete robot, mission, or alert investigation.
01 What the screen shows
detailsTotals
The summary shows total robots, online count, utilization (online / total), mission success rate (completed / (completed + failed + cancelled)), and active alerts. Treat a zero denominator as no available history, then open the fleet or mission screen to investigate an unexpected value.
Filters
Choose cohort_id or tag using the same selection model as the fleet board. Both are reflected in the URL, so teammates can open the same slice rather than trying to recreate filters from a screenshot.
Troubleshooting
- Utilization is zero
- Check whether the filtered selection has robots and whether any currently report online. The value is online divided by total, not time-based utilization.
- Mission success looks lower than expected
- Cancelled missions are included with failed missions in the denominator. Review mission terminal states for the selected slice.
- An API client cannot find the endpoint
- This is an authenticated console view, not a public machine API. Use the underlying documented operator or fleet surfaces for automation.