> 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/1-7-2/documentation/agents/monitoring.md).
# Monitoring
## Status
The connectivity status of the agents can be monitored by navigating to `System > System Status > Agents` in the UI.
In the table of currently known agents, for each agent the current status (*online* / *offline*) is shown, as well as the version number of this particular agent container, and the hostname as configured when starting the agent container.
Agents in *offline* status can be removed from this list by pressing the `Delete` icon in the upper right corner after selecting that row in the table. Note: This merely removes the agent from the list, but it does *not remove a registered user* from the user database! To remove a registered agent user from the user database, go to the “User Management” page in the Admin-UI and delete that particular user, see [Deleting Users](/1-7-2/documentation/user-management/users.md#deleting-users).
## Docker Logs
The docker logs (or: debug output) of the agent containers *can not be monitored* from within Connectware. Instead, those logs need to be monitored by the chosen [orchestration tool (above)](/1-7-2/documentation/agents/installation.md#orchestration) that is also responsible for the container deployment.
---
# 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/1-7-2/documentation/agents/monitoring.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.
