chore(tracing): Use upstream tracing batch exporter

sfleen · sfleen · commit 208b6b96674a · 2025-11-17T10:46:29.000-05:00
The proxy used its own custom trace exporter for some time. It was built before the upstream OpenTelemetry libraries were available, and they have outlived their usefulness.

This replaces the custom exporter with a batch exporter configured to export to the same endpoint with the same service configuration.

In the future, this exporter can be installed as a global default trace processor, which would decouple it from the service layer where the proxy generates spans for requests.

Signed-off-by: Scott Fleener &lt;scott@buoyant.io&gt;
diff --git a/linkerd/opentelemetry/src/lib.rs b/linkerd/opentelemetry/src/lib.rs
@@ -185,6 +185,8 @@ fn convert_span(span: ExportSpan) -> Result<SpanData, Error> {
 mod tests {
     use super::*;
     use linkerd_trace_context::{export::SpanKind, Id, Span};
+    use opentelemetry_proto::tonic::common::v1::any_value::Value::StringValue;
+    use opentelemetry_proto::tonic::common::v1::AnyValue;
     use opentelemetry_proto::tonic::common::v1::InstrumentationScope;
     use std::{collections::HashMap, sync::Arc, time::SystemTime};
     use tokio::sync::mpsc;
