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
{{ message }}
This repository has been archived by the owner on May 23, 2024. It is now read-only.
The Java client has a feature where codecs can be specified via the env var JAEGER_PROPAGATION. Here's its description:
Comma separated list of formats to use for propagating the trace context. Defaults to the standard Jaeger format. Valid values are jaeger and b3
This issue is to bring the feature to the Go client. Currently, only jaeger is automatically set. The following code can be used to add the Zipkin to the tracer options:
the big downside in Go if we support this feature is that the config module starts to depend on all other modules, whether the end user needs them or not. I think it is an anti-pattern in Go.
The Java client has a feature where codecs can be specified via the env var
JAEGER_PROPAGATION
. Here's its description:This issue is to bring the feature to the Go client. Currently, only
jaeger
is automatically set. The following code can be used to add the Zipkin to the tracer options:And here's the relevant code in the Java client:
https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/src/main/java/com/uber/jaeger/Configuration.java#L437-L462
The text was updated successfully, but these errors were encountered: