Feat Request: Support W3C Trace Context header
Closed this issue · 6 comments
W3C trace context now is "W3C Recommendation 06 February 2020"
But nginx-opentracing support B3 and jaeger, not support w3c trace context.
I know opentelemetry support W3c trace context dafault, but still many people use nginx-opentracing( specaily nginx-ingress-controller)
+1
It seems the Jaeger CPP should support W3C Format https://www.jaegertracing.io/docs/1.18/client-libraries/#propagation-format
Here is an open PR: https://github.com/jaegertracing/jaeger-client-cpp/pull/255/files
I also need this with a aspnet core backend . The backend only knows how to get the parent context if it is in W3C format.
I have successfully upgraded jaeger tracer to custom branch: master...miry:upgrade-jeager-opentracing
It generates W3C format headers.
Going to prepare a PR.
Also there is an improvement PR to have trace 128 bits jaegertracing/jaeger-client-cpp#254
Created a sample PR #147 to show how it is possible to use latest Jaeger with W3C. There are no any changes required in nginx-opentracing code.
Working on patching nginx-ingress to support latest libs.
Jeager tracing released a new version where it supports W3C headers.
Ingress-nginx master has changes with latest jaeger.
So now it is possible to use nginx-opentracing with a new Jaeger and support W3C headers.