Internal Telemetry

Bindplane OTel collectors expose internal telemetry metrics using the Prometheus format.

NOTE

📗 Configure the global telemetry port for a Bindplane Server (Self-Hosted), here.

Starting with Bindplane Server v1.90.1, you can configure the telemetry port on a per-configuration basis using the Advanced Configuration settings. This allows different configurations to use different telemetry ports.

IMPORTANT

You can assign the port per configuration but not per agent. Hosts that cannot use the default port 8888 will need to be added to a configuration with a different port configured.

NOTE

See the May 9, 2025 release notes for more information.

OpenTelemetry Internal Telemetry

Bindplane uses OpenTelemetry's internal telemetry configuration. For more details about the upstream OpenTelemetry telemetry implementation, see the OpenTelemetry Internal Telemetry documentation.

NOTE

The upstream OpenTelemetry schema had a breaking change regarding telemetry configuration.

Some time ago, service.telemetry.metrics.address was deprecated in favor of service.telemetry.metrics.readers. BDOT agents v1.74.1 to v1.82.0 support both schemas. Depending on the version of Bindplane you are using, the generated configuration may use different field names.