-
Notifications
You must be signed in to change notification settings - Fork 988
[main] Add B3 trace IDs to cf cli commands #3310
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
Conversation
1683294 to
8057cbf
Compare
37b425f to
2203c4e
Compare
a-b
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2203c4e to
ed61add
Compare
|
@Samze any update on this PR? |
This dropped off my radar over the holidays, hope to pick this back up and finish it off in the next week or two. |
gururajsh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #3309
Description of the Change
The CLI now sets the B3_TRACE headers as per https://docs.cloudfoundry.org/adminguide/distributed-tracing.html#unique-trace-id.
Notes:
X-B3-Traceidheader for all API requests initiated by that CF command. (e.g. use the same header for all api calls for the commandcf apps).X-B3-Spanidper API request.CF_B3_TRACE_IDthat allows theX-B3-Traceidto be overridden.X-Vcap-Request-Idto the same header as theX-B3-Traceid(in uuid v4 format) and will work withW3Cheaders if `router.tracing.enable_w3c is set.CF_TRACEor-vWhy Is This PR Valuable?
See #3309
Examples
With auto-generated headers:
With environment variable override: