> 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-1-0/documentation/monitoring.md).

# Monitoring

Real-time insights into your data.

Monitoring data helps maintain system performance and allows for quick issue resolution in data flows. Connectware includes monitoring tools for observing services and their resources.

Connectware offers the following monitoring options:

* Service-Specific View: The **Live Data** tab shows real-time data for a selected service.
* System-Wide View: The **Data Explorer** displays all data flows in Connectware.

The **Data Explorer** view shows all MQTT topics connected to Connectware, providing an overview of the entire system. This allows for analysis of interactions between different services and components. For more information, see [Data Explorer](/2-1-0/documentation/monitoring/data-explorer.md).

The **Live Data** tab focuses on MQTT topics for a single selected service, useful for monitoring individual services. For more information, see [Live Data](/2-1-0/documentation/monitoring/live-data.md).


---

# 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-1-0/documentation/monitoring.md?ask=<question>&goal=<user_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.