open_telemetry_collector
Sends metrics to one or more OpenTelemetry Collector endpoints.
Exports Redpanda Connect metrics to one or more OpenTelemetry Collector endpoints, encoded with the OpenTelemetry metrics protocol (OTLP). Any collector endpoint that supports OTLP can receive them.
You can configure HTTP and gRPC endpoints at the same time. Every configured endpoint receives the same metrics, which is useful for redundancy or for sending metrics to several 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