Bump tracing-opentelemetry from 0.16.0 to 0.17.4

[dependabot]

Bumps tracing-opentelemetry from 0.16.0 to 0.17.4.

Release notes

Sourced from tracing-opentelemetry's releases.

tracing-opentelemetry 0.17.4

This release adds optional support for recording std::error::Errors using [OpenTelemetry's semantic conventions for exceptions][exn-semconv].

Added

• Layer::with_exception_fields to enable emitting exception.message and exception.backtrace semantic-convention fields when an Error is recorded as a span or event field (#2135)
• Layer::with_exception_field_propagation to enable setting exception.message and exception.backtrace semantic-convention fields on the current span when an event with an Error field is recorded (#2135)

Thanks to @​lilymara-onesignal for contributing to this release!

#2135: tokio-rs/tracing#2135

tracing-opentelemetry 0.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 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 according to OpenTelemetry semantic conventions (#2134)
• Error::source chain when recording std::error::Error values (#2122)
• Layer::with_location method (replaces Layer::with_event_location) (#2124)

Changed

• std::error::Error values are now recorded using fmt::Display rather than fmt::Debug (#2122)

Fixed

• Fixed event source code locations overwriting the parent span's source location (#2099)
• Fixed Layer::with_event_location not controlling whether locations are emitted for spans as well as events (#2124)

Deprecated

• Layer::with_event_location: renamed to Layer::with_location, as it now controls both span and event locations (#2124)

Thanks to new contributors @​lilymara-onesignal, @​hubertbudzynski, and @​DevinCarr

... (truncated)

Commits

• 6752895 opentelemetry: prepare to release v0.17.4 (#2202)
• beb227b chore(bin): fix bin/publish script running cargo publish twice
• 9638587 subscriber: prepare to release v0.3.14 (#2201)
• 2659ccf opentelemetry: fix exception fields defaults in docs (#2200)
• 4a3f299 attributes: ensure res and err events inherit target (#2184)
• e0b3f79 subscriber: fix max_level_hint for empty Option/Vec Layer impls (#2195)
• 0012a41 subscriber: \<None as Layer>::event_enabled should be true (#2193)
• 2fdbaaa subscriber: prepare to release v0.3.13 (#2192)
• 7f62097 subscriber: fix clippy lints (#2191)
• b4680b1 subscriber: update minimum tracing-core dep to 0.1.28 (#2190)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)