#env-var #log #logging #logger

env_filter

Filter log events using environment variables

3 releases

new 0.1.2 Jul 25, 2024
0.1.1 Jul 23, 2024
0.1.0 Jan 19, 2024

#252 in Debugging

Download history 236410/week @ 2024-04-04 233362/week @ 2024-04-11 238122/week @ 2024-04-18 230150/week @ 2024-04-25 237580/week @ 2024-05-02 235924/week @ 2024-05-09 239524/week @ 2024-05-16 241583/week @ 2024-05-23 280546/week @ 2024-05-30 287124/week @ 2024-06-06 291798/week @ 2024-06-13 287511/week @ 2024-06-20 282868/week @ 2024-06-27 292102/week @ 2024-07-04 328019/week @ 2024-07-11 301053/week @ 2024-07-18

1,254,230 downloads per month
Used in 1,615 crates (8 directly)

MIT/Apache

48KB
971 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.9–4MB
~69K SLoC