lumbermill 0.0.3

Simple structured logging
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105

# 🪓 lumbermill

[![Crates.io](https://img.shields.io/crates/v/lumbermill.svg)](https://crates.io/crates/lumbermill)
[![Documentation](https://docs.rs/lumbermill/badge.svg)](https://docs.rs/lumbermill)

Simple structured logging.

![Screenshot of log output](./examples/logs.png)

### Usage

```rust
use lumbermill::{info, Logger}

fn main() {
  // Initialize the logger early
  Logger::default().init();

  // Log a single line
  info!("Incoming connection from {:?} {}", addr, port);

  // Attach key-value pairs with the log message
  info!(addr.ip = ip, addr.port = port, "Listening on {}", port);
  // Or use the shorthand if the key's name is the same as the variable:
  info!(addr.ip, port, "Listening on {}", port);

  // Attach key-value pairs with the log message, formatting them using their
  // `Debug` trait (useful when variables do not implement `Display`)
  info!(addr.ip = ?ip, addr.port = port, "Listening on {}", port);
  // Or in the shorthand notation:
  info!(?addr.ip, port, "Listening on {}", port);
}
```

The `trace!`, `debug!`, `info!`, `warn!`, `error!` & `fatal!` are heavily inspired
by `tracing`'s macros because they're good.

The default logger prints pretty logs to `stdout` only, but you can configure the `Logger` to behave differently:

```rust
use lumbermill::{LogFormat, LogLevel, RollInterval};

Logger::builder()
  .format(LogFormat::Compact) // Set the format of logs
  .level(LogLevel::Info) // Set the minimum log level
  .stdout(false) // Stop printing to stdout
  .file("./logs", RollInterval::Daily) // Log to a directory; one file per day

  // Shorthands
  .pretty() //  .format(LogFormat::Pretty)
  .compact() // .format(LogFormat::Compact)
  .json() // .format(LogFormat::Json)

  // Remember to call `init` after configuration!
  .init();
```

You can have different active configurations in different scenarios by using the
`#![cfg]` macro:

```rust
// Pretty logs on stdout during development
#[cfg(debug_assertions)]
Logger::default().level(LogLevel::Trace).pretty().init();

// Compact logs on rolling files in production
#[cfg(not(debug_assertions))]
{
  let dir = "./logs";
  std::fs::create_dir_all(dir)?;
  Logger::default()
    .level(LogLevel::Info)
    .compact()
    .file(dir, lumbermill::RollInterval::Hourly)
    .init();
}
```

### Examples

[Examples](https://github.com/sdnts/lumbermill-rs/tree/main/examples) are a good entrypoint to learn about the library. Run them this way:

```sh
$ cargo run --example 01-defaults # Or replace this wil a different example's name
```

[Docs](https://docs.rs/lumbermill) usually go into more detail once you get the hang of things.

### Why?

The `tracing` ecosystem is awesome, but it's also overkill for a lot of apps who
only need structured logging and not a distributed tracing solution. The `log` crate
is the obvious alternative, but its `kv` module is a work-in-progress.
You are also unable to log key-value pairs that do not implement `Display`, in
a incovenient way.

This crate is a stop-gap till `log::kv` stabilizes. It marries `tracing`'s awesome
`event!` macro to `log`'s simplicity. The plan is to eventually drop the custom
macros in this crate and integrate with `log` directly.

### Credits

- [tracing](https://docs.rs/tracing)
- [tracing_appender](https://docs.rs/tracing_appender)
- [log](https://docs.rs/log)