Eliza Weisman
ea7178b8c6
This branch improves the `fmt::Debug` implementation for `Metadata`, and adds `fmt::Display` implementations for `FieldSet` and `ValueSet`. When formatting a `Metadata`, only present fields are formatted --- if optional fields, such as the file, line number, and module path are `None`, they will be excluded. In addition, `Metadata` now formats its `FieldSet` using `FieldSet`'s `fmt::Display` implementation, which is a bit less noisy. Finally, the `Debug` output for `Metadata` now includes the callsite that the metadata originates from. The intention behind these changes is to make the output from failed tests somewhat easier to interpret. Signed-off-by: Eliza Weisman <[email protected]>
tokio-trace-core
Core primitives for tokio-trace.
Overview
tokio-trace is a framework for instrumenting Rust programs to collect
structured, event-based diagnostic information. This crate defines the core
primitives of tokio-trace.
The crate provides:
-
Spanidentifies a span within the execution of a program. -
Eventrepresents a single event within a trace. -
Subscriber, the trait implemented to collect trace data. -
Field,FieldSet,Value, andValueSetrepresent the structured data attached to aSpan. -
Dispatchallows span events to be dispatched toSubscribers.
In addition, it defines the global callsite registry and per-thread current dispatcher which other components of the tracing system rely on.
Application authors will typically not use this crate directly. Instead, they
will use the tokio-trace crate, which provides a much more fully-featured
API. However, this crate's API will change very infrequently, so it may be used
when dependencies must be very stable.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tokio by you, shall be licensed as MIT, without any additional terms or conditions.