-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
🧩 Feature Request: Support Pushing Metrics to OpenTelemetry Collector
Summary
It would be valuable for the connector-service
to support emitting and exporting metrics to an OpenTelemetry (OTel) Collector, enabling better observability and integration with existing monitoring pipelines.
Motivation
Adding OTel support would provide the following benefits:
- Unified observability stack with other components of the system
- Standardized metric formats (OTLP)
- Easy forwarding of metrics to Prometheus, Grafana, or third-party observability platforms (e.g., Datadog, New Relic)
- Supports cloud-native practices and improves debuggability
This is especially useful in environments where metrics collection needs to be centralized and scalable.
Proposed Solution
Integrate OpenTelemetry metrics support using crates such as:
opentelemetry
opentelemetry-otlp
- (Optional)
metrics
with an OpenTelemetry bridge
Example Initialization (OTLP Exporter):
use opentelemetry::sdk::metrics::controllers;
use opentelemetry::sdk::metrics::processors;
use opentelemetry::sdk::export::metrics::aggregation;
use opentelemetry_otlp::WithExportConfig;
let exporter = opentelemetry_otlp::new_exporter()
.tonic()
.with_endpoint("http://otel-collector:4317");
let meter_provider = controllers::basic(processors::factory(
aggregation::cumulative_temporality_selector(),
opentelemetry::sdk::metrics::selectors::simple::Selector::Exact,
))
.with_exporter(exporter)
.build();
opentelemetry::global::set_meter_provider(meter_provider);
Metadata
Metadata
Assignees
Labels
No labels