# Any plan for support opentracing baggage? **URL:** \ **Category:** APM\ **Tags:** go, java, python\ **Created:** [May 24, 2019, 2:20pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672 "2019-05-24T14:20:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dozer47528](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dozer47528/32/46811_2.png) [@dozer47528](https://discuss.elastic.co/u/dozer47528)\ **Post date:** [May 24, 2019, 2:20pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/1 "2019-05-24T14:20:00Z")
We are working on the Jaeger to Elastic APM migrating. We are using the opentracing baggage in our system. Everything works fine with Elastic APM except baggage. Any plan for that? ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [May 24, 2019, 2:28pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/2 "2019-05-24T14:28:34Z")
Hi and thanks for your question. Out of curiosity: what are you using the baggage for in your application? Is it essential for you in order to be able to migrate or is it a (very?) nice-to-have? ---
**Author:** ![dozer47528](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dozer47528/32/46811_2.png) [@dozer47528](https://discuss.elastic.co/u/dozer47528)\ **Post date:** [May 24, 2019, 2:57pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/3 "2019-05-24T14:57:18Z")
Thank for replay. We used it for propagating the context in our cluster between different service. For example, the login user id, request id. I knew we can do it manually by read it from HTTP header and add them to the next HTTP request. But the baggage is useful for us. For our migrating process, we need to rewrite all of these codes. ---
**Author:** ![dozer47528](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dozer47528/32/46811_2.png) [@dozer47528](https://discuss.elastic.co/u/dozer47528)\ **Post date:** [May 24, 2019, 3:07pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/4 "2019-05-24T15:07:02Z")
Elastic APM has the ability to propagate the tracing content, it looks easy to propagate baggage. What's more, Elastic APM is compatible with opentracing specification, baggage is part of opentracing specification. ---
**Author:** ![axw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/axw/32/28197_2.png) [@axw](https://discuss.elastic.co/u/axw)\ **Post date:** [May 27, 2019, 1:15am UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/5 "2019-05-27T01:15:59Z")
At the moment we don't have any plans to do this. I think if we were to support baggage, it would most likely be by implementing [https://github.com/w3c/correlation-context](https://github.com/w3c/correlation-context), which is not yet finalised. ---
**Author:** ![dozer47528](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dozer47528/32/46811_2.png) [@dozer47528](https://discuss.elastic.co/u/dozer47528)\ **Post date:** [May 27, 2019, 5:20pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/6 "2019-05-27T17:20:03Z")
Thanks for this info, we will do this part by ourself. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2019, 1:20pm UTC](https://discuss.elastic.co/t/any-plan-for-support-opentracing-baggage/182672/7 "2019-06-17T13:20:15Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.