> For the complete documentation index, see [llms.txt](https://docs.dextoros.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dextoros.app/fleet-and-console/fleet-dashboard-and-history.md).

# Fleet dashboard and history

Live telemetry, status and the full event history for every robot.

{% hint style="warning" %}
**Draft.** Some details on this page are still being confirmed and may change. Questions? Email <info@dextoros.app>.
{% endhint %}

DextorOS shows live telemetry, commands and the full event history for each machine, whatever the maker.

## The fleet list

The **Fleet** list shows every connected robot with its ID, platform and current activity. Filter it by **all**, **online** or **offline**.

A robot's activity is one of:

* Working
* Idle
* Moving to a bay
* Docking
* Charging, with its battery level
* Homing
* Paused
* Offline, with how long it has been offline

## Telemetry

Each robot streams telemetry that fits its body:

{% columns %}
{% column %}

### Arms

| Field      | Unit           |
| ---------- | -------------- |
| Motor temp | °C             |
| Cycle time | s              |
| Gripper    | Open or Closed |
| Latency    | ms             |

Arms also show the angle of each joint, `J1` to `J6`.
{% endcolumn %}

{% column %}

### Mobile and legged robots

| Field            | Unit                              |
| ---------------- | --------------------------------- |
| Battery          | %                                 |
| Speed            | m/s                               |
| Location         | On dock, a bay, or x, y in metres |
| Latency          | ms                                |
| {% endcolumn %}  |                                   |
| {% endcolumns %} |                                   |

A chart tracks each robot's link latency over the last 48 seconds. When a robot is offline, its fields show **No data** or **No signal** and its last known battery level.

## History and activity log

Every robot keeps a full history, and the activity log is searchable. Each entry is one of four types:

| Type    | Example                                    |
| ------- | ------------------------------------------ |
| `cmd`   | `> move_to B3`                             |
| `ack`   | `Moving to bay B3. Accepted in 38 ms`      |
| `event` | `Docked. Charging`                         |
| `error` | `Unknown bay "E4". Bays run from A1 to D9` |

Events include connections, completed cycles, arrivals, charging, lost heartbeats and alerts sent by [rules](/automation/rules.md), for example:

```
Connected over ROS 2, 3 capabilities reported
Battery below 25%. Automation sent it to the dock
No heartbeat for 60 s. Connection lost
Offline alert sent to the on-call operator
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dextoros.app/fleet-and-console/fleet-dashboard-and-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.