tree: feaa086538e6a854fecd0bd58ba1e954325a2c7c [path history] [tgz]
  1. .cargo-checksum.json
  2. .cargo_vcs_info.json
  3. .travis.yml
  5. Cargo.toml
  9. appveyor.yml
  10. src/
  11. tests/


A Rust library providing a lightweight logging facade.

Build Status Build status Latest version Documentation License

A logging facade provides a single logging API that abstracts over the actual logging implementation. Libraries can use the logging API provided by this crate, and the consumer of those libraries can choose the logging implementation that is most suitable for its use case.


In libraries

Libraries should link only to the log crate, and use the provided macros to log whatever information will be useful to downstream consumers:

log = "0.4"
extern crate log;

pub fn shave_the_yak(yak: &mut Yak) {
    trace!("Commencing yak shaving");

    loop {
        match find_a_razor() {
            Ok(razor) => {
                info!("Razor located: {}", razor);
            Err(err) => {
                warn!("Unable to locate a razor: {}, retrying", err);

In executables

In order to produce log output executables have to use a logger implementation compatible with the facade. There are many available implementations to chose from, here are some of the most popular ones:

Executables should choose a logger implementation and initialize it early in the runtime of the program. Logger implementations will typically include a function to do this. Any log messages generated before the logger is initialized will be ignored.

The executable itself may use the log crate to log as well.