Core primitives for application-level tracing.
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::Id
identifies a span within the execution of a program. -
Event
represents a single event within a trace. -
Collect
, the trait implemented to collect trace data. -
Metadata
andCallsite
provide information describing spans and events. -
Field
,FieldSet
,Value
, andValueSet
represent the structured data attached to spans and events. -
Dispatch
allows spans and 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.
Compiler support: requires rustc
1.49+
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.
Subscriber
implementations may depend on tracing-core
rather than tracing
,
as the additional APIs provided by tracing
are primarily useful for
instrumenting libraries and applications, and are generally not necessary for
Subscriber
implementations.
The following crate feature flags are available:
-
std
: Depend on the Rust standard library (enabled by default).no_std
users may disable this feature withdefault-features = false
:[dependencies] tracing-core = { version = "0.1.17", default-features = false }
Note:
tracing-core
'sno_std
support requiresliballoc
.
Tracing is built against the latest stable release. The minimum supported version is 1.49. The current Tracing version is not guaranteed to build on Rust versions earlier than the minimum supported version.
Tracing follows the same compiler support policies as the rest of the Tokio project. The current stable Rust compiler and the three most recent minor versions before it will always be supported. For example, if the current stable compiler version is 1.45, the minimum supported version will not be increased past 1.42, three minor versions prior. Increasing the minimum supported compiler version is not considered a semver breaking change as long as doing so complies with this policy.
This project is licensed under the MIT license.
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.