> 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/configuration/bindplane/collector-telemetry-port.md).

# Collector Telemetry Port

Bindplane OTel collectors expose internal telemetry metrics using the Prometheus format. By default, these metrics are available on TCP port 8888.

{% hint style="info" %}
**NOTE**

[📗 Configure the per-organization telemetry port for a Bindplane, here.](/configuration/bindplane-otel-collector/internal-telemetry.md)
{% endhint %}

For self-hosted Bindplane server deployments, you can configure the collector's telemetry port globally, which affects all collectors managed by Bindplane.

## Configuration File

Add the `agent.telemetryPort` option to the `advanced` section of your Bindplane configuration file:

```yaml
advanced:
  agent:
    telemetryPort: 8888
```

{% hint style="info" %}
**NOTE**

See the [June 19, 2024 release notes](https://docs.bindplane.com/changelog/june-2024/2024-06-19-release#agent-metrics-port) for more information.
{% endhint %}

## Server Flag

When starting the Bindplane server, use the `--advanced-agent-telemetry-port` flag:

```bash
bindplane serve --advanced-agent-telemetry-port 8888
```

## Environment Variable

Set the `BINDPLANE_ADVANCED_AGENT_TELEMETRY_PORT` environment variable:

```bash
export BINDPLANE_ADVANCED_AGENT_TELEMETRY_PORT=8888
```


---

# 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/configuration/bindplane/collector-telemetry-port.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.