> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/production-checklist/bindplane-otel-collector/monitoring.md).
# Monitoring
To monitor collector logs, we will set up the Bindplane Distro for OpenTelemetry (BDOT) Collector source that will send log files from the Collector itself. These logs contain information about the health of your BDOT Collector.
For this, we will need an already deployed collector from any existing configuration you already have set up. No additional server configuration is needed, we will just go into any of the configurations you would like to gather Collector logs from and click 'Add Source'. From there select the 'Bindplane Collector' source like in the example below:
We can leave this on default as well for this example, and simply click 'Save':
All that is left is to push out the configuration to the Collectors by running a "Start Rollout". With that source rolled out to the Collector machines, your Bindplane Collector logs will now be sent to the destination of your choice. Below is an example of those logs on a Google Cloud Destination:
{% hint style="info" %}
**NOTE**
📘 Adding processors to this collector could cause problems, as it would create entries in this same log file, which could lead to infinite error messages. Add any processors sparingly and thoroughly test afterward to ensure it is following the intended behavior.
{% endhint %}
If you haven't yet, you can also set up [monitoring of the Bindplane server itself.](/production-checklist/bindplane/monitoring-bindplane.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.bindplane.com/production-checklist/bindplane-otel-collector/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.
