tracing/tracing-serde
Eliza Weisman 6a5cb28a44
meta: rename everything to tracing (#99)
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>
2019-06-26 11:31:07 -07:00
..

tracing-serde

An adapter for serializing tracing types using serde.

Documentation

Overview

tracing-serde enables serializing tracing types using serde. tracing is a framework for instrumenting Rust programs to collect structured, event-based diagnostic information.

Traditional logging is based on human-readable text messages. tracing gives us machine-readable structured diagnostic information. This lets us interact with diagnostic data programmatically. With tracing-serde, you can implement a Subscriber to serialize your tracing types and make use of the existing ecosystem of serde serializers to talk with distributed tracing systems.

Serializing diagnostic information allows us to do more with our logged values. For instance, when working with logging data in JSON gives us pretty-print when we're debugging in development and you can emit JSON and tracing data to monitor your services in production.

The tracing crate provides the APIs necessary for instrumenting libraries and applications to emit trace data.

Usage

First, add this to your Cargo.toml:

[dependencies]
tracing = "0.1"
tracing-serde = "0.1"

Next, add this to your crate:

#[macro_use]
extern crate tracing;
extern crate tracing_serde;

use tracing_serde::AsSerde;

Please read the tracing documentation for more information on how to create trace data.

This crate provides the as_serde function, via the AsSerde trait, which enables serializing the Attributes, Event, Id, Metadata, and Record tracing values.

For the full example, please see the examples folder.

Implement a Subscriber to format the serialization of tracing types how you'd like.

pub struct JsonSubscriber {
    next_id: AtomicUsize, // you need to assign span IDs, so you need a counter
}

impl Subscriber for JsonSubscriber {

    fn new_span(&self, attrs: &Attributes) -> Id {
        let id = self.next_id.fetch_add(1, Ordering::Relaxed);
        let id = Id::from_u64(id as u64);
        let json = json!({
        "new_span": {
            "attributes": attrs.as_serde(),
            "id": id.as_serde(),
        }});
        println!("{}", json);
        id
    }
    // ...
}

After you implement your Subscriber, you can use your tracing subscriber (JsonSubscriber in the above example) to record serialized trace data.

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.