
See #95 This branch renames everything from `tokio-trace` to `tracing`. Unlike PR #98, the nursery crates still depend on the crates.io versions of `tokio-trace` and `tokio-trace-core`, but renamed to `tracing`/`tracing-core` in `Cargo.toml`. We can update the nursery crates to depend on local path dependencies in a subsequent PR, as that will require making code changes to the nursery crates. This branch _also_ updates the minimum Rust version to 1.34.0, to the shock and horror of the millions of `tracing` users still on Rust 1.26.0. This was necessary in order to allow renaming crates in `Cargo.toml`, and to resolve that not using the `dyn` keyword is now a warning on nightly. Closes #98 Closes #95 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
2.3 KiB
tracing-core
Core primitives for tracing
.
Overview
tracing
is a framework for instrumenting Rust programs to collect
structured, event-based diagnostic information. This crate defines the core
primitives of tracing
.
The crate provides:
-
Span
identifies a span within the execution of a program. -
Event
represents a single event within a trace. -
Subscriber
, the trait implemented to collect trace data. -
Field
,FieldSet
,Value
, andValueSet
represent the structured data attached to aSpan
. -
Dispatch
allows span events to be dispatched toSubscriber
s.
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 tracing
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.