> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/monitoring/live-data.md).
# Live Data
MQTT topic traffic and resource insights for a single service.
The **Live Data** tab allows you to monitor MQTT topics of the selected service directly in the **Service Details** view. Live data provide insights into topic activity, message content, and associated resources.
For monitoring all MQTT topics, use the [Data Explorer](/2-6-1/monitoring/data-explorer.md).
* To open the **Live Data** view, click **Services** and click a service to open the **Service Details** view. In this view, click **Live Data**.
**Search**
* Find specific resources or resource IDs. Topics are not searchable.
**Resource ID**
* The unique identifier for the resource. You can click the **Resource ID** for more information on the resource.
**Resource Type**
* The type of the resource. Available types include:
* Endpoint
* Node
* Mapping
**Topics**
* The complete path of the MQTT topic.
**Message**
* The data transmitted by the topic, formatted in JSON.
Example:
{% code lineNumbers="true" %}
```yaml
{ 'timestamp': 1730908287298, 'value': [] }
```
{% endcode %}
**Time**
* The timestamp indicating when the data was sent.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.cybus.io/2-6-1/monitoring/live-data.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
