Skip to content
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

tracer: support b3multi alias for b3 carrier #1594

Merged
merged 2 commits into from Nov 23, 2022
Merged

Conversation

katiehockman
Copy link
Contributor

What does this PR do?

Adds b3multi as a supported propagator for trace context extraction and injection, which will act as a new alias for the existing b3 propagator.

Motivation

This is to align with the OTel specification.

Describe how to test/QA your changes

Set DD_PROPAGATION_STYLE_INJECT and DD_PROPAGATION_STYLE_EXTRACT to "b3" and ensure that any headers headers propagate as expected. Then do the same for setting it to "b3multi" and verify that the behavior didn't change.

Reviewer's Checklist

  • If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
  • Changed code has unit tests for its functionality.
  • If this interacts with the agent in a new way, a system test has been added.

@katiehockman katiehockman changed the title support b3multi alias for b3 header tracer: support b3multi alias for b3 carrier Nov 22, 2022
@katiehockman katiehockman added this to the v1.45.0 milestone Nov 22, 2022
@katiehockman katiehockman changed the title tracer: support b3multi alias for b3 carrier tracer: support b3multi alias for b3 carrier Nov 22, 2022
@katiehockman katiehockman marked this pull request as ready for review November 22, 2022 19:48
@katiehockman katiehockman requested review from a team and removed request for a team November 22, 2022 19:48
ddtrace/tracer/textmap_test.go Outdated Show resolved Hide resolved
Co-authored-by: Andrew Glaude <andrew.glaude@datadoghq.com>
@pr-commenter
Copy link

pr-commenter bot commented Nov 22, 2022

Benchmarks

Found 0 performance improvements and 0 performance regressions! Performance is the same for 6 cases.

Copy link
Contributor

@ajgajg1134 ajgajg1134 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! :)

@katiehockman katiehockman merged commit 5ac4f70 into main Nov 23, 2022
@katiehockman katiehockman deleted the katiehockman/w3c branch November 23, 2022 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants