#env-var #log #logging #logger

env_filter

Filter log events using environment variables

1 unstable release

0.1.0 Jan 19, 2024

#189 in Debugging

Download history 42769/week @ 2024-01-21 75045/week @ 2024-01-28 86307/week @ 2024-02-04 104142/week @ 2024-02-11 103981/week @ 2024-02-18 123059/week @ 2024-02-25 147698/week @ 2024-03-03 163114/week @ 2024-03-10 193954/week @ 2024-03-17 186005/week @ 2024-03-24 214806/week @ 2024-03-31 232606/week @ 2024-04-07 236189/week @ 2024-04-14 240576/week @ 2024-04-21 231366/week @ 2024-04-28 228092/week @ 2024-05-05

951,973 downloads per month
Used in 1,220 crates (3 directly)

MIT/Apache

37KB
709 lines

env_filter

crates.io Documentation

Filter log events using environment variables


lib.rs:

Filtering for log records.

You can use the Filter type in your own logger implementation to use the same filter parsing and matching as env_logger.

Using env_filter in your own logger

You can use env_filter's filtering functionality with your own logger. Call Builder::parse to parse directives from a string when constructing your logger. Call Filter::matches to check whether a record should be logged based on the parsed filters when log records are received.

use env_filter::Filter;
use log::{Log, Metadata, Record};

struct PrintLogger;

impl Log for PrintLogger {
    fn enabled(&self, metadata: &Metadata) -> bool {
        true
    }

    fn log(&self, record: &Record) {
        println!("{:?}", record);
    }

    fn flush(&self) {}
}

let mut builder = env_filter::Builder::new();
// Parse a directives string from an environment variable
if let Ok(ref filter) = std::env::var("MY_LOG_LEVEL") {
    builder.parse(filter);
}

let logger = env_filter::FilteredLog::new(PrintLogger, builder.build());

Dependencies

~2.8–4MB
~68K SLoC