-
Notifications
You must be signed in to change notification settings - Fork 292
CP-53161: Baggage
threaded through smapi
and back into xapi
#6278
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
Merged
edwintorok
merged 4 commits into
xapi-project:master
from
GabrielBuica:private/dbuica/CP-53161
Mar 14, 2025
Merged
CP-53161: Baggage
threaded through smapi
and back into xapi
#6278
edwintorok
merged 4 commits into
xapi-project:master
from
GabrielBuica:private/dbuica/CP-53161
Mar 14, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3cc819e
to
4558f24
Compare
These changes append the `baggage` of the `trace_context` to the list of environment variables that are about to be submitted to SM scripts by `forkexec`. This should improve the propagation of `trace_context` along traces that use multiple components. Signed-off-by: Gabriel Buica <danutgabriel.buica@cloud.com>
This links requests back into `xapi` from `smapi` to the xapi request that called the SM scripts in the first place. When `smapi` was experimental there would be no traceparent header passed in the request from `smapi` to `xapi`. Now, when `smapi` is experimental and the tracing is enabled for xapi, the traceparent passed to `smapi` is passed back to `xapi` for each request. Signed-off-by: Gabriel Buica <danutgabriel.buica@cloud.com>
4558f24
to
f4465eb
Compare
psafont
approved these changes
Feb 27, 2025
lindig
reviewed
Feb 27, 2025
edwintorok
approved these changes
Mar 3, 2025
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.
Can you squash the fixup into the commit, that should fix the failing DCO test.
xs-aidan
reviewed
Mar 3, 2025
When a the baggage is passed as an environment variable, it is now added to the resource attributes inside of `observer.py`. Signed-off-by: Gabriel Buica <danutgabriel.buica@cloud.com>
Just as the traceparent is passed back as an additional header, now the baggage is passed as well in the http request coming from `smapi` back into `xapi`. Signed-off-by: Gabriel Buica <danutgabriel.buica@cloud.com>
29faa32
to
87a4a5a
Compare
snwoods
approved these changes
Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It continues the path of threading the
trace_context
across different components. Specifically, fromxapi
tosmapi
and back toxapi
.Additional improvement: the tracecontext is passed even when
smapi
component is experimental and it does not create spans. Therefore, it is not creating orphaned spans from http requests made to xapi.BVT+BST: 213297