Update to opentelemetry 0.24 #907
Merged
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
|
Tests are broken upstream. Fix is in #908. |
joshwlewis
force-pushed
the
jwl/otel-update
branch
from
fc13411 to
be8e613
Compare
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.
This updates opentelemetry to the last version that supports JSONL file exports -- at least for the moment. There was an upstream change to simplify the
opentelemetry-stdoutexporter: open-telemetry/opentelemetry-rust#2040. With that change, the exporter lost the ability to send telemetry to a generic writer (like a buffer or file), and also lostjsonlserialization. Based on this comment, there is interest in bringing this functionality back in some other form.I've opened an issue upstream: open-telemetry/opentelemetry-rust#2602
Supersedes #886