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
for contributing to this release!

tracing-core 0.1.27

This release of tracing-core introduces a new DefaultCallsite type, which
can be used by instrumentation crates rather than implementing their own
callsite types. Using DefaultCallsite may offer reduced overhead from callsite
registration.

Added

• DefaultCallsite, a pre-written Callsite implementation for use in
  instrumentation crates (#2083)
• ValueSet::len and Record::len methods returning the number of fields in a
  ValueSet or Record (#2152)

Changed

• Replaced lazy_static dependency with once_cell (#2147)

Documented

• Added documentation to the callsite module (#2088, #2149)

Thanks to new contributors @jamesmunns and @james7132 for contributing to this
release!

tracing-attributes 0.1.21

This release adds support for setting explicit parent and follows-from spans
in the #[instrument] attribute.

Added

• #[instrument(follows_from = ...)] argument for setting one or more
  follows-from span (#2093)
• #[instrument(parent = ...)] argument for overriding the generated span's
  parent (#2091)

Fixed

• Extra braces around async blocks in expanded code (causes a Clippy warning)
  (#2090)
• Broken documentation links (#2068, #2077)

Thanks to @jarrodldavis, @ben0x539, and new contributor @jswrenn for
contributing to this release!

tracing-log 0.1.3

Added

• log-tracer: Added LogTracer::with_interest_cache to enable a limited
  form of per-record Interest caching for log records (#1636)

Changed

• Updated minimum supported Rust version (MSRV) to Rust 1.49.0 (#1913)

Fixed

• log-tracer: Fixed LogTracer not honoring tracing max level filters
  (#1543)
• Broken links in documentation (#2068, #2077)

Thanks to @Millione, @teozkr, @koute, @Folyd, and @ben0x539 for contributing to
this release!

tracing-journald 0.3.0

This is a breaking release which changes the format in which span fields
are output to journald. Previously, span field names were prefixed with the
depth of the span in the current trace tree. However, these prefixes are
unnecessary, as journald has built in support for duplicated field names.

See PR #1986 for details on this change.

Changed

• Removed span field prefixes (#1986)
• Renamed S{num}_NAME fields to SPAN_NAME (#1986)

Fixed

• Fixed broken links in documentation (#2077)

Thanks to @wiktorsikora and @ben0x539 for contributing to this release!

tracing-core 0.1.26

This release adds a Value implementation for Box<T: Value> to allow
recording boxed values more conveniently. In particular, this should improve
the ergonomics of the implementations for dyn std::error::Error trait objects,
including those added in v0.1.25.

Added

• Value implementation for Box<T> where T: Value (#2071)

Fixed

• Broken documentation links (#2068)

Thanks to new contributor @ben0x539 for contributing to this release!

tracing 0.1.34

This release includes bug fixes for the "log" support feature and for the use of
both scoped and global default dispatchers in the same program.

Fixed

• Failure to use the global default dispatcher when a thread sets a local
  default dispatcher before the global default is set (#2065)
• log: Compilation errors due to async block/fn futures becoming !Send
  when the "log" feature flag is enabled (#2073)
• Broken links in documentation (#2068)

Thanks to @ben0x539 for contributing to this release!

tracing-core 0.1.25

This release adds additional Value implementations for std::error::Error
trait objects with auto trait bounds (Send and Sync), as Rust will not
auto-coerce trait objects. Additionally, it fixes a bug when setting scoped
dispatchers that was introduced in the previous release (v0.1.24).

Added

• Value implementations for dyn Error + Send + 'static, dyn Error + Send + Sync + 'static, dyn Error + Sync + 'static (#2066)

Fixed

• Failure to use the global default dispatcher if a thread has set a scoped
  default prior to setting the global default, and unset the scoped default
  after setting the global default (#2065)

Thanks to @lilyball for contributing to this release!

tracing-subscriber 0.3.11

This is a bugfix release for the Filter implementation for EnvFilter added
in v0.3.10.

Fixed

• env-filter: Added missing Filter::on_record callback to EnvFilter's
  Filter impl (#2058)
• env-filter: Fixed method resolution issues when calling EnvFilter
  methods with both the Filter and Layer traits in scope (#2057)
• env-filter: Fixed EnvFilter::builder().parse() and other parsing methods
  returning an error when parsing an empty string (#2052)

Thanks to new contributor @Ma124 for contributing to this release!

tracing 0.1.33

This release adds new span_enabled! and event_enabled! variants of the
enabled! macro, for testing whether a subscriber would specifically enable a
span or an event.

Added

• span_enabled! and event_enabled! macros (#1900)
• Several documentation improvements (#2010, #2012)

Fixed

• Compilation warning when compiling for <=32-bit targets (including wasm32)
  (#2060)

Thanks to @guswynn, @arifd, @hrxi, @CAD97, and @name1e5s for contributing to
this release!