cli-log

The boilerplate to have some file logging with a level given by an environment variable, and a facility to log execution durations according to the relevant log level.

It's convenient for terminal applications because you don't want to mix log with stdout or stderr.

And the use of an env variable makes it possible to distribute the application and have users generate some logs without recompilation or configuration.

The names of the log file and the env variable are computed from the name of the application.

So log initialization is just

cli_log::init("my-app");

Import

In Cargo.toml:

log = "0.4"
cli-log = "0.1"

Usage

Here's a complete application using cli-log (it can be found in examples):

```

[macro_use] extern crate log;

[macrouse] extern crate clilog;

[derive(Debug)]

struct AppData { count: usize, } impl AppData { fn compute(&mut self) { self.count += 7; } }

fn main() { clilog::init("small-app"); let mut appdata = AppData { count: 35 }; time!(Debug, appdata.compute()); info!("count is {}", appdata.count); debug!("data: {:#?}", &app_data); warn!("this application does nothing"); info!("bye"); } ```

If you don't set any SMALL_APP_LOG env variable, there won't be any log.

A convenient way to set the env variable is to launch the app as

cli SMALL_APP_LOG=debug small-app

or, during development,

cli SMALL_APP_LOG=debug cargo run

This creates a small-app.log file containing information like the level, app version, and of course the log operations you did with time precise to the ms and the logging module (target):

11:45:37.565 [INFO] cli_log: Starting small-app v0.1.0 with log level DEBUG 11:45:37.565 [DEBUG] small_app: app_data.compute() took 198ns 11:45:37.565 [INFO] small_app: count is 42 11:45:37.565 [DEBUG] small_app: data: AppData { count: 42, } 11:45:37.565 [WARN] small_app: this application does nothing 11:45:37.565 [INFO] small_app: bye

This log file can typically be followed with tail -f small_app.log.