4 releases

0.1.3 Dec 20, 2024
0.1.2 Jul 25, 2024
0.1.1 Jul 23, 2024
0.1.0 Jan 19, 2024

#177 in Debugging

Download history 346875/week @ 2024-12-21 473177/week @ 2024-12-28 767132/week @ 2025-01-04 895010/week @ 2025-01-11 806976/week @ 2025-01-18 918765/week @ 2025-01-25 942910/week @ 2025-02-01 1001328/week @ 2025-02-08 904396/week @ 2025-02-15 1005275/week @ 2025-02-22 1258847/week @ 2025-03-01 1213599/week @ 2025-03-08 1414499/week @ 2025-03-15 1763961/week @ 2025-03-22 1156917/week @ 2025-03-29 1237425/week @ 2025-04-05

5,774,637 downloads per month
Used in 3,488 crates (10 directly)

MIT/Apache

48KB
971 lines

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());

env_filter

crates.io Documentation

Filter log events using environment variables

Dependencies

~2.7–4MB
~68K SLoC