Some context for ☝️: added the opentracing agent instead of the opentelemery agent to a react frontend (communicating with a dotnet backend with an otel tracer).
need to determine if switching to opentelemetry and redoing auto. and manual instrumentation would be easier than trying to get opentracing agent to always use w3c headers.
Hi, I have a problem with https://github.com/opentracing-contrib/java-spring-cloud. I can't use the latest version of Spring Boot and Spring Cloud OpenFeign because of classpath problems.
The PR opentracing-contrib/java-spring-cloud#324 would solve the problem but it is open since Apr 26.
Could someone look at it and merge the PR if everything is OK?
@yurishkuro Just got it now.
In parent side, the code below gets a map with key "uber-trace-id" for Jaeger.
textCarrier := opentracing.TextMapCarrier{}
err := span.Tracer().Inject(span.Context(), opentracing.TextMap, textCarrier)
Then I can get parent context like
textCarrier := opentracing.TextMapCarrier{"uber-trace-id": "2975a5cc24621e8a:2975a5cc24621e8a:0000000000000000:1"}
spanCtx, err := tracer.Extract(opentracing.TextMap, textCarrier)
All I need to transport that encoded string. Nice :)
In "https://opentracing.io/guides/golang/spans/" under "Passing of scopes to another thread or callback is not supported.", there is such a statement:
Passing of scopes to another thread or callback is not supported.
Does it mean that answer of my question is "It is not possible. "?
Also, if I have a project currently using the OpenTracing API, is it advisable to migrate it to the OpenTelemetry API?
Thank you