Bug: 153120834

Clone this repo:
  1. 9d6d114 Allow using liblog_rust from DnsResolver by Bernie Innocenti · 7 weeks ago master
  2. 57a2421 Mark ab/6881855 as merged by Xin Li · 9 weeks ago
  3. 5da2859 TEST_MAPPING: test dependers of this crate am: ed2cd6cfa4 by Jeff Vander Stoep · 3 months ago
  4. ed2cd6c TEST_MAPPING: test dependers of this crate by Jeff Vander Stoep · 3 months ago
  5. aacce58 Copy description from Cargo.toml to METADATA am: db11ffc281 by Chih-Hung Hsieh · 4 months ago


A Rust library providing a lightweight logging facade.

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.

Minimum supported rustc


This version is explicitly tested in CI and may be bumped in any release as needed. Maintaining compatibility with older compilers is a priority though, so the bar for bumping the minimum supported version is set very high. Any changes to the supported minimum version will be called out in the release notes.


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"
use log::{info, trace, warn};

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 choose 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.