
## Motivation The `tracing-core::dispatcher` module is currently somewhat under-documented, which has caused confusion for many users. There should be a detailed description of how traces are dispatched, and the different methods of setting a default subscriber. In addition, the `tokio` feature flag that enables automatic dispatcher propagation is undocumented, which has also caused issues (see #169). ## Solution This branch adds new module-level docs to the `dispatcher` module, including examples of how default subscribers are set. It also corrects a factual error in the documentation for `with_default`. Signed-off-by: Eliza Weisman <eliza@buoyant.io>
tracing-core
Core primitives for application-level 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.