Dynamically change log level after `init`

[hasezoey]

Is there currently a way to change the log level after having called init already? If there is currently no way, i would like to request this feature

Use case: i would like to enable logging as the first thing in my code to have log output (from env, etc) and later after having parsed the cli (like with clap) set the level based on something like verbosity. also another use case would be to dynamically turn the logging on / off for a specific part (which is probably already covered by #144)

[wiz21b]

I'd like to mention that I have a similar use case. I have tried to disable logging before initializing the builder but it doesn't work. I've also tried to send all the log to a sink target, but it doesn't work either. It seems that the RUST_LOG env. variable takes priority over the settings of the builder...

This is what I do:

log_builder.filter(None, LevelFilter::Error);
log_builder.target(env_logger::Target::Pipe(sink));
log_builder.init();

[morrisonlevi]

You don't need env_logger to change the log level as the log crate already provides log::set_max_level.

[hasezoey]

You don't need env_logger to change the log level as the log crate already provides log::set_max_level.

the documentation says Generally, this should only be called by the active logging implementation., is env_logger fine with it being change outside of itself?

[KodrAus]

I think you might get strange results calling set_max_level directly, since env_logger "compiles" the max level into its filters, those aren't derived on-the-fly from the max level set in log.

[epage]

btw #113 looks somewhat related