mirror of https://github.com/tokio-rs/tracing.git synced 2025-10-02 07:20:35 +00:00

History

core: add fmt::Debug impl to dyn Values (#696 )

## Motivation

Currently, the only way to interact with `Value`s is to record them with
a visitor. In the most common case, where typed data is not needed,
`Value`s are recorded with their `fmt::Debug` implementations — a
visitor which does not implement the `record_${TYPE}` traits will
automatically fall back to recording all primitive value types with
`Debug`. However, implementing a visitor requires a bit of boilerplate:
an entire trait implementation has to be written, and a visitor object 
passed to `record`.

## Solution

This branch hopes to simplify this common case by adding a `Debug` 
implementation to _all_ `dyn Value` trait objects. This is equivalent
to a visitor that only implements `record_debug`, but requiring less
boilerplate.

Signed-off-by: Eliza Weisman <eliza@buoyant.io>

2020-05-04 17:48:55 -07:00

src

core: add fmt::Debug impl to dyn Values (#696 )

2020-05-04 17:48:55 -07:00

tests

core: Add set_default method to set default dispatcher (#388 )

2019-10-18 11:56:33 -07:00

Cargo.toml

chore: clean up old CI stuff (#670 )

2020-04-07 10:52:01 -07:00

CHANGELOG.md

core: prepare to release 0.1.10 (#598 )

2020-02-24 11:31:59 -08:00

LICENSE

meta: rename everything to tracing (#99 )

2019-06-26 11:31:07 -07:00

README.md

core: prepare to release 0.1.10 (#598 )

2020-02-24 11:31:59 -08:00

README.md

tracing-core

Core primitives for application-level tracing.

Documentation | Chat

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::Id 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.
Metadata and Callsite provide information describing spans and events.
Field, FieldSet, Value, and ValueSet represent the structured data attached to spans and events.
Dispatch allows spans and events to be dispatched to Subscribers.

In addition, it defines the global callsite registry and per-thread current dispatcher which other components of the tracing system rely on.

Usage

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.

Crate Feature Flags

The following crate feature flags are available:

std: Depend on the Rust standard library (enabled by default).

no_std users may disable this feature with default-features = false:
```
[dependencies]
tracing-core = { version = "0.1.10", default-features = false }
```
Compiler support: requires rustc 1.39+

Note:tracing-core's no_std support requires liballoc.

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.