mirror of
https://github.com/tokio-rs/tracing.git
synced 2025-10-02 07:20:35 +00:00
2520f97964
## Motivation As discussed in #308, there are a large number of crates in this repository, which can be confusing for users and can increase the maintainance burden for maintainers. Also, the `tracing-fmt` and `tracing-subscriber` crates both contain filtering implementations with similar behaviour and APIs, but `tracing-subscriber`'s filter module offers more advanced features (filtering on field values), and is usable with any subscriber implementation. Two separate filter implementations also has the potential to be confusing for users. ## Solution This branch moves most of the code from `tracing-fmt` into a module in `tracing-subscriber`, and changes the `tracing-fmt` builder APIs to use the `Filter` type in `tracing-subscriber`. The `tracing-subscriber/fmt` feature flag can be used to disable the formatting subscriber when it is not used. The `tracing-fmt` crate has been updated to re-export the APIs from `tracing-subscriber`, and marked as deprecated. Once we've published a new version of `tracing-subscriber` with the format APIs, we can publish a final release of `tracing-fmt` that will update the documentation & mark all APIs as deprecated, so that users know to move to the `tracing-subscriber` crate. Refs: #308 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
21 lines
507 B
Rust
21 lines
507 B
Rust
#![deny(rust_2018_idioms)]
|
|
use tracing::debug;
|
|
|
|
mod yak_shave;
|
|
|
|
fn main() {
|
|
let subscriber = tracing_subscriber::fmt::Subscriber::new();
|
|
|
|
tracing::subscriber::with_default(subscriber, || {
|
|
let number_of_yaks = 3;
|
|
debug!("preparing to shave {} yaks", number_of_yaks);
|
|
|
|
let number_shaved = yak_shave::shave_all(number_of_yaks);
|
|
|
|
debug!(
|
|
message = "yak shaving completed.",
|
|
all_yaks_shaved = number_shaved == number_of_yaks,
|
|
);
|
|
});
|
|
}
|