open_telemetry_collector
Send metrics to an Open Telemetry collector.
Exports Redpanda Connect metrics to one or more OpenTelemetry Collector endpoints over HTTP or gRPC for aggregation and onward export.
Metrics are encoded using the OpenTelemetry Metrics protocol and can be sent to any collector endpoint that supports OTLP.
You can configure multiple collector endpoints (both HTTP and gRPC simultaneously). All configured endpoints will receive the same metrics data. This is useful for redundancy or sending metrics to multiple observability platforms.
-
Common
-
Advanced
metrics:
open_telemetry_collector:
service: benthos
http: [] # No default (required)
grpc: [] # No default (required)
metrics:
open_telemetry_collector:
service: benthos
http: [] # No default (required)
grpc: [] # No default (required)
tags: {}
Fields
Usage
The most common setup uses a local OpenTelemetry Collector running as a sidecar or daemon, which then forwards metrics to your observability backend:
metrics:
open_telemetry_collector:
service: my-service-name
grpc:
- address: localhost:4317
For production deployments with remote collectors, enable TLS:
metrics:
open_telemetry_collector:
service: my-service-name
grpc:
- address: otel-collector.example.com:4317
secure: true
Use the tags field to add labels to all exported metrics for filtering and grouping in your observability platform:
metrics:
open_telemetry_collector:
service: my-service-name
grpc:
- address: localhost:4317
tags:
environment: production
cluster: kafka-01