tracing
tracing copied to clipboard
tokio-rs
Application level tracing for Rust.
this doesn't _quite_ work yet, but i thought it could be nice to have --- possibly @jtescher has some advice on how to handle remote parents nicely (and, if i'm...
This branch adds the ability to set a scoped dispatcher for all threads globally, which is unset when a RAII guard is dropped. See #1517. The global scoped default is...
## Feature Request As of now only `set_global_default` is only reliable way to set logger available to all threads within application. While `set_default`/`with_default` actually sets logger onto thread local hence...
## Motivation `RollingAppender::new` uses `expect` to handle any `InnerAppender` error: ```rust RollingFileAppender { inner: InnerAppender::new( directory.as_ref(), file_name_prefix.as_ref(), rotation, Utc::now(), ).expect("Failed to create appender"), } ``` I found it may be...
## Feature Request ### Crates `tracing-serde` ### Motivation Currently, `tracing-serde` supports serializing `tracing` types, such as `Metadata`, `Event`, `span::Attributes` and `span::Record`, etc. However, it does not support _deserializing_ those types...
## Motivation Disabling the logging of spans by `fmt` while still recording them with a distributed tracing system like OpenTelemetry, is one that isn't nicely solved by the filtering system...
This branch is a draft implementation of a potential redesign of the `tracing-subscriber` Registry API. In the new design, a `Registry` is a type which _wraps_ a stack of subscribers...
## Motivation The unused parameters always need to be skipped in most cases. However, keep writing `#[tracing::instrument(skip(_arg1, _arg2))]` is unnecessary and unconcise. Rarely, someone would use underscore parameter as normal,...
## Motivation We use a lot of data that's encoded as bytes that we would like to record to spans and events. While it's possible to use the debug representation,...
## Motivation Previously, the tests for `std::future` support were always compiled, regardless of whether or not the `std::future` feature was enabled. This is because the tests were in the integration...