You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zipkin exporter support will be removed from OpenTelemetry in Jan 2027.
9
+
Zipkin exporter support will be removed from OpenTelemetry specification in Jan 2027.
10
10
11
11
_Note: This document remains here for backwards compatibility and
12
12
will be removed in a future version. SDKs MAY include Zipkin exporters,
13
-
but Zipkin export is not required.
14
-
Users may export to Zipkin using [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)_
13
+
but Zipkin exporter is not required.
14
+
15
+
Users may export to Zipkin using [zipkin exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter) collector component or [zipkin-otel](https://github.com/openzipkin-contrib/zipkin-otel)
16
+
Zipkin server module_
15
17
16
18
This document defines the transformation between OpenTelemetry and Zipkin Spans.
17
19
The generic transformation [rules specified here](../../common/mapping-to-non-otlp.md) also apply. If a
@@ -76,7 +78,7 @@ not work properly. OpenTelemetry doesn't provide this consistency guarantee.
76
78
Exporter may chose to override the value for service name based on a local root
77
79
span to improve Zipkin user experience.
78
80
79
-
*Note*, the attribute `service.namespace` MUST NOT be used for the Zipkin
81
+
_Note_, the attribute `service.namespace` MUST NOT be used for the Zipkin
0 commit comments