#env-var #log #logging #logger

env_filter

Filter log events using environment variables

1 unstable release

0.1.0 Jan 19, 2024

#190 in Debugging

Download history 10325/week @ 2024-01-16 54307/week @ 2024-01-23 77151/week @ 2024-01-30 93122/week @ 2024-02-06 103888/week @ 2024-02-13 103161/week @ 2024-02-20 129044/week @ 2024-02-27 152403/week @ 2024-03-05 173796/week @ 2024-03-12 194995/week @ 2024-03-19 177575/week @ 2024-03-26 227712/week @ 2024-04-02 236488/week @ 2024-04-09 193087/week @ 2024-04-16

870,724 downloads per month
Used in 1,078 crates (2 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