-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tracing: support getting/setting baggage on spans #11622
Comments
Can't it just be a no-op. |
I think NOP is probably fine to start with, but I could imagine some uses cases in which people would think they are sending baggage and it doesn't actually do anything in practice? |
What are your thoughts on logging a warning to avoid failing silently in tracers that do not support baggage (i.e. in the no-op methods)? |
with #12260 merged do we want to close this issue? Or we do we want to leave it as a tracker for other Tracer's not-yet-implemented functionality? |
I think we can close for now, thank you! |
The Envoy span API:
envoy/include/envoy/tracing/http_tracer.h
Line 108 in 9aa85a3
Does not support getting/setting baggage. At Lyft we will need to make use of this against the OT driver so will need to add this support. It should be fairly trivial to call through to the OT driver code for this but will need to figure out how to handle this generically for tracers that do not support baggage (possibly a feature capability bit or similar).
cc @rnburn @objectiser @garrettheel
The text was updated successfully, but these errors were encountered: