tracing: Replace deprecated jaeger exporter with otelhttp exporter #14928
Conversation
This file contains 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
prestonvanloon
force-pushed
the
otel-exporter
branch
from
fa137e0 to
f2b50c2
Compare
kasey
reviewed
Feb 14, 2025
kasey
approved these changes
Feb 15, 2025
nalepae
pushed a commit
that referenced
this pull request
Feb 20, 2025
…14928) * Update go.opentelemetry.io/otel to v1.34.0 * Update otel exporter to replace deprecated jaeger exporter * Changelog * Use WithEndpointURL * Clarify potential breaking change
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.
What type of PR is this?
Other
What does this PR do? Why is it needed?
The jaeger exporter is deprecated:
Jaeger supports otel http anyway. This shouldn't be a breaking change.
Which issues(s) does this PR fix?
Other notes for review
Draft until testing in Offchain Labs infra.
Acknowledgements