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
Currently, there is no direct association between Observation and Baggage.
If I want to use baggage, I need to interact with Tracer API. Then, the code needs to mix observation and tracing, which I feel reduces the value of the observation abstraction.
How about tracing-observation-handler to have a list of observation tags that will be converted to baggage?
Currently, there is no direct association between
Observation
andBaggage
.If I want to use baggage, I need to interact with Tracer API. Then, the code needs to mix observation and tracing, which I feel reduces the value of the observation abstraction.
How about tracing-observation-handler to have a list of observation tags that will be converted to baggage?
For example,
When
Observation
hasfoo.id
tag, it will be treated as baggage.It would be nice to integrate
Observation
andBaggage
to eliminate the Tracer API usage in user code for baggage.The text was updated successfully, but these errors were encountered: