slog-rs - Structured, composable logging for Rust

Documentation

Introduction

Inspired by [log15] for Go.

Features

• easy to use
• hierarchical loggers
• lazily evaluated values
• modular and extensible
  • small core create with multiple addon crates (./crates/) - compile only what you're actually using
• standard log crate logging support (slog-stdlog crate)
• drains & output formatting
  • filtering
  • multiple outputs
  • asynchronous IO writing
  • terminal output, with color support (slog-term crate)
  • Json (slog-json crate)
    • Bunyan (slog-bunyan crate)
  • syslog (slog-syslog crate)
  • support for first class custom ones

Advantages over log create

• composable and extensible logging drains - You can easily log messages to different destinations, in different formats, using different filtering rules. Building new drains and new output formats is very easy.
• drains are run-time swappable - Send a signal to your program and start logging everything to a file for run-time production debugging. Send another one when you're done to return to normal operation. Build your own flexible scenarios easily.
• non-global - Hierarchical loggers carry information about context of logging. When logging an error condition, you want to know which resource was being handled, on which instance of your service, using which source code build, talking with what peer, etc. In standard log you would have to repeat this information in every log statement. In slog it will happen automatically.
• both human and machine readable - By keeping the key-value data format, meaning of logging data is preserved. Dump your logging to a JSON file, and send it to your data-mining system for further analysis.
• lazy evaluation and asynchronous IO included

Terminal output example

Using & help

Code snippet

``rust fn main() { // Create a new group of loggers, sharing one drain. // // Noteo!macro for more naturalOwnedKeyValue` sequence building. let root = Logger::new_root(o!("version" => VERSION, "build-id" => "8dfljdf"));

// Set drains to specify the output format and destination.
root.set_drain(slog_term::async_stderr());

// Build logging context as data becomes available.
//
// Create child loggers from existing ones. Children clone `key: value`
// pairs from their parents.
let log = root.new(o!("child" => 1));

// Closures can be used for values that change at runtime.
// Data captured by the closure needs to be `Send+Sync`.
let counter = Arc::new(AtomicUsize::new(0));
let log = log.new(o!("counter" => {
    let counter = counter.clone();
    // Note the `move` to capture `counter`,
    // and unfortunate `|_ : &_|` that helps
    // current `rustc` limitations. In the future,
    // a `|_|` could work.
    move |_ : &_| { counter.load(SeqCst)}
}));

// Note `b!` macro for more natural `BorrowedKeyValue` sequence building.
log.info("before-fetch-add", b!()); // counter == 0
counter.fetch_add(1, SeqCst);
log.info("after-fetch-add", b!()); // counter == 1

// Drains can be swapped atomically (race-free).
log.set_drain(
    // drains are composable
    drain::filter_level(
        Level::Info,
        drain::stream(
            drain::async(std::io::stderr()),
            // multiple outputs formats are supported
            slog_json::new(),
            ),
        ),
    );

// Closures can be used for lazy evaluation:
// This `slow_fib` won't be evaluated, as the current drain discards
// "trace" level logging records.
log.debug("debug", b!("lazy-closure" => |_ : &_| slow_fib(40)));

// Loggers are internally atomically reference counted so can be cloned,
// passed between threads and stored without hassle.
let join = thread::spawn({
    let log = log.clone();
    move || {
        log.info("subthread", b!("stage" => "start"));
        thread::sleep(Duration::new(1, 0));
        log.info("subthread", b!("stage" => "end"));
    }
});

join.join().unwrap();

} ```

See examples/features.rs for full code.

Read Documentation for details and features.

If you want to say hi, or need help use #dpc gitter.im.

To report a bug or ask for features use github issues.

Building & running

If you need to install Rust (come on, you should have done that long time ago!), use rustup.

In your project

In Cargo.toml:

[dependencies] slog = "*"

In your main.rs:

```

[macro_use]

extern crate slog; ```