David Mládek
David Mládek
## Motivation Closes #1531 There are scenarios where one wants to add some information to logs emitted by `FmtSubscriber`, for example adding OpenTelemetry trace ID and span ID. ## Solution...
## Motivation Closes #2935 Builds on #2936 Parsing of filters checking for field values is broken when used with more than one field. There may be multiple directives split by...
## Motivation The timings measurements were done naively in a way where they added `busy` time in `on_exit` and `idle` time in `on_enter. This works only if the spans are...
## Motivation `valuable` support has had unstable support for two years now with no major issues. The crate has close to 30 million downloads on crates.io and all its dependants...
## Feature Request ### Crates `tracing-subscriber` ### Motivation The timings shouldn't be tracked by the formatting subscribe. It's implementation was probably also copied when `tracing-opentelemetry` was created and now there...
## Bug Report ### Version Current master (908cc432), probably all prior versions since addition of `set_default`. ### Crates `tracing-core` ### Description When a local default `Dispatch` is set, a guard...
## Motivation Some tests were ignored with a TODO to enable them. The doc-test for `Subscriber::record` provides misleading code that does not compile. ## Solution I enabled the tests that...
Ref #2651 and #2659 ## Motivation Nesting at `/foo` and `/foo/` is almost the same but isn't consistent in whether the root route is at `/foo` or at `/foo/`. More...
This would allow extracting body to `BytesMut`. This should have exactly the same performance as collecting to `Bytes`, if there is more than one buf in the `BufList`, but it...
## Motivation An alternative to #2655. Currently, `tracing-core` defines a `tracing` feature which is never used, because it was intended only for expansion inside a macro, but the `#[cfg(feature =...