fix(telemetry): bump otel to resolve panicks in layered span access #820
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.
Summary
Update tracing-opentelemetry to 0.23.0 to resolve panics
Background
We are seeing panics with backtraces pointing to either code provides json formatted fields, or to tracing-opentelemetry layers. This patch upgrades
astria-telemetry
to use tracing-opentelemetry 0.23 (and bumps related crates) to try and resolve that.Changes
Bump the following crates
Related Issues
tokio-rs/tracing-opentelemetry#86