opentelemetry: prepare to release v0.17.3 #2154
Merged
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.
0.17.3 (June 7, 2022)
This release adds support for emitting thread names and IDs to
OpenTelemetry, as well as recording
std::error::Error
values in astructured manner with their source chain included. Additionally, this
release fixes issues related to event and span source code locations.
Added
Layer::with_threads
to enable recording thread names/IDs accordingto OpenTelemetry semantic conventions (#2134)
Error::source
chain when recordingstd::error::Error
values(#2122)
Layer::with_location
method (replacesLayer::with_event_location
)(#2124)
Changed
std::error::Error
values are now recorded usingfmt::Display
rather than
fmt::Debug
(#2122)Fixed
location (#2099)
Layer::with_event_location
not controlling whether locationsare emitted for spans as well as events (#2124)
Deprecated
Layer::with_event_location
: renamed toLayer::with_location
, as itnow controls both span and event locations (#2124)
Thanks to new contributors @lilymara-onesignal, @hubertbudzynski,
and @DevinCarr for contributing to this release!