fix(deps): update rust crate tracing-opentelemetry to 0.28.0 #1044
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 PR contains the following updates:
0.13.0
->0.28.0
Release Notes
tokio-rs/tracing-opentelemetry (tracing-opentelemetry)
v0.28.0
: 0.28.0Compare Source
What's Changed
Layer::on_close
by @mzabaluev in https://github.com/tokio-rs/tracing-opentelemetry/pull/173v0.27.0
Compare Source
Breaking Changes
changelog
for more information.
v0.26.0
Compare Source
Breaking Changes
changelog
for more information.
v0.25.0
Compare Source
Breaking Changes
changelog
for more information.
Fixed
v0.24.0
Compare Source
Breaking Changes
changelog
for more information.
Added
Fixed
v0.23.0
Compare Source
Breaking Changes
changelog
for more information. In particular, i64 histograms will silently downgrade to
key/value exports.
v0.22.0
Compare Source
Breaking Changes
v0.21.0
ofopentelemetry
For list of breaking changes in OpenTelemetry, see the
v0.21.0 changelog.
opentelemetry
requires it now. (#68)Fixed
Thanks to @jesseditson, @AsmPrgmC3, and @rthomas for contributing to this release!
v0.21.0
Compare Source
Added
Breaking Changes
MetricsLayer
is now generic over the itsSubscriber
impl to supportper-layer filtering (#43)
Fixed
Thanks to @ymgyt and @hdost for contributing to this release!
v0.20.0
Compare Source
Added
OpenTelemetrySpanExt::set_attribute
function (#34)Breaking Changes
v0.20.0
ofopentelemetry
(#36)For list of breaking changes in OpenTelemetry, see the
v0.20.0 changelog.
Thanks to @ymgyt, @mladedav, @shaun-cox, and @Protryon for contributing to this release!
v0.19.0
Breaking Changes
v0.19.0
ofopentelemetry
(#12)For list of breaking changes in OpenTelemetry, see the
v0.19.0 changelog.
opentelemetry
requires it now (#12)Thanks to @jaysonsantos, @briankung, and @humb1t for contributing to this release!
v0.18.0
Breaking Changes
v0.18.0
ofopentelemetry
([#2303])For list of breaking changes in OpenTelemetry, see the
v0.18.0 changelog.
Fixed
on_event
respects event's explicit parent ([#2296])Thanks to @wprzytula for contributing to this release!
v0.17.4
This release adds optional support for recording
std::error::Error
s using[OpenTelemetry's semantic conventions for exceptions][exn-semconv].
Added
Layer::with_exception_fields
to enable emittingexception.message
andexception.backtrace
semantic-convention fields when anError
is recordedas a span or event field (#2135)
Layer::with_exception_field_propagation
to enable settingexception.message
andexception.backtrace
semantic-convention fields on the current span when anevent with an
Error
field is recorded (#2135)Thanks to @lilymara-onesignal for contributing to this release!
v0.17.3
This release adds support for emitting thread names and IDs to OpenTelemetry, as
well as recording
std::error::Error
values in a structured manner with theirsource 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 according toOpenTelemetry 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 thanfmt::Debug
(#2122)Fixed
location (#2099)
Layer::with_event_location
not controlling whether locations areemitted for spans as well as events (#2124)
Deprecated
Layer::with_event_location
: renamed toLayer::with_location
, as it nowcontrols both span and event locations (#2124)
Thanks to new contributors @lilymara-onesignal, @hubertbudzynski, and @DevinCarr
for contributing to this release!
v0.17.2
This release fixes an issue introduced in v0.17.1 where
tracing-opentelemetry
could not be compiled withdefault-features = false
.Fixed
tracing-log
feature disabled (#1949)v0.17.1
Added
OpenTelemetryLayer
can now add detailed location information toforwarded events (defaults to on) (#1911)
OpenTelemetryLayer::with_event_location
to control whether source locationsare recorded (#1911)
Changed
(#1917)
Thanks to @djc for contributing to this release!
v0.17.0
Breaking Changes
v0.17.0
ofopentelemetry
(#1853)For list of breaking changes in OpenTelemetry, see the
v0.17.0 changelog.
v0.15.0
Breaking Changes
v0.17.1
ofopentelemetry
(#1497)For list of breaking changes in OpenTelemetry, see the
v0.17.1 changelog.
v0.14.0
Breaking Changes
v0.15.0
ofopentelemetry
(#1441)For list of breaking changes in OpenTelemetry, see the
v0.14.0 changelog.
Added
code.namespace
,code.filepath
, andcode.lineno
attributes (#1411)Changed
Vec
s (#1327)Thanks to @Drevoed, @lilymara-onesignal, and @Folyd for contributing
to this release!
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.