-
|
Today we default to jaeger-thrift and B3 to support SFx instrumentation and smart agent. Given SA deprecation, should we default to standards and document how to change if not ready to migrate yet? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
Most languages (may be all) support composite propagators that allow combining multiple propagators into one. Node and I think Java do this today to enable both B3 and W3C propagators at the same time. We can do this today for all libs and remove B3 way past SFX deprecation. |
Beta Was this translation helpful? Give feedback.
-
|
I believe Bogdan said this does not work and B3/W3C may conflict in some ways... I do not know enough about this, but if we could confirm that would be great |
Beta Was this translation helpful? Give feedback.
-
|
multi-extraction definitely isn't a problem, as far as I know. I wonder what Bogdan's concerns were. |
Beta Was this translation helpful? Give feedback.
-
|
As far as I've seen it works fine. Composite propagator injects both B3 and W3C headers. Extract tries all until it finds a valid context. |
Beta Was this translation helpful? Give feedback.
-
|
Multi-extraction is not a problem, but multi-injection can be. I remember some customer of ours did not want too much extra headers, because they wanted to propagate context propagation via S3 headers and they have a low cap on the number of headers. |
Beta Was this translation helpful? Give feedback.
-
|
How many customers face such issues? If it is only a small number of customers, we can still default to composite propagator while allowing users to specify just B3 or W3C. |
Beta Was this translation helpful? Give feedback.
-
|
Plan is to move forward with this -- see #50 |
Beta Was this translation helpful? Give feedback.
Plan is to move forward with this -- see #50