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

maint: Replace baggage span processor with OTel version #383

Closed
wants to merge 6 commits into from

Conversation

MikeGoldsmith
Copy link
Contributor

Which problem is this PR solving?

Replaces the distro's custom baggage span processor with the newly contributed OTel baggage activity processor.

Short description of the changes

  • Remove custom bagage span processor
  • Add OpenTelemetry.Extensions package that includes the processor
  • Use baggage processor during tracer provider configuration
  • Add NoWarn for NU1605 to ignore the dependency requirement of the new package - we don't want to move past 1.6.0 to preserve HTTP semcomv compatability - see here

@MikeGoldsmith MikeGoldsmith added the type: maintenance The necessary chores to keep the dust off. label May 8, 2024
@MikeGoldsmith MikeGoldsmith self-assigned this May 8, 2024
@MikeGoldsmith MikeGoldsmith requested a review from a team as a code owner May 8, 2024 20:46
Copy link
Member

@cartermp cartermp left a comment

Choose a reason for hiding this comment

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

red diffs best diffs

@MikeGoldsmith
Copy link
Contributor Author

We're not going to go ahead with this for now as it requires users to also ignore the NU1605 warning. This is because the new OTel baggage processor requires the latest SDK version 1.8.1 and we don't want to move our distro beyond 1.6.0 for HTTP semcomv breaking changes.

We'll come back to this in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance The necessary chores to keep the dust off.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants