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

#170 in Debugging

Download history 863882/week @ 2025-01-21 909792/week @ 2025-01-28 959519/week @ 2025-02-04 958674/week @ 2025-02-11 951937/week @ 2025-02-18 995896/week @ 2025-02-25 1314088/week @ 2025-03-04 1215123/week @ 2025-03-11 1662372/week @ 2025-03-18 1501405/week @ 2025-03-25 1182096/week @ 2025-04-01 1223076/week @ 2025-04-08 998170/week @ 2025-04-15 1049390/week @ 2025-04-22 967259/week @ 2025-04-29 875377/week @ 2025-05-06

4,097,418 downloads per month
Used in 3,739 crates (13 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.8–4MB
~68K SLoC