#env-var #logging #log #logger

env_filter

Filter log events using environment variables

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

#144 in Debugging

Download history 862361/week @ 2024-11-15 737071/week @ 2024-11-22 621493/week @ 2024-11-29 737560/week @ 2024-12-06 734096/week @ 2024-12-13 391479/week @ 2024-12-20 433547/week @ 2024-12-27 719412/week @ 2025-01-03 897656/week @ 2025-01-10 820305/week @ 2025-01-17 901702/week @ 2025-01-24 937166/week @ 2025-01-31 991903/week @ 2025-02-07 899721/week @ 2025-02-14 1018228/week @ 2025-02-21 907000/week @ 2025-02-28

3,983,856 downloads per month
Used in 3,180 crates (9 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.8–4MB
~68K SLoC