Closed CodingAnarchy closed 9 months ago
Thanks!
Actually, the DEBUG level isn't a great choice either, as it makes debugging your own code difficult due to the crate's logs polluting the output.
I suggest changing the log level to TRACE, which is defined as "Designates very low priority, often extremely verbose, information." (and this is the case actually).
Another approach is to use tracing_subscriber
crate and to override the crate logs level like RUST_LOG=gcp_auth=NONE, ...
.
I'm happy to review a PR that adjusts logging levels.
Maybe later, I'm too busy with the project. Sorry.
Also, I managed to mute the noisy logs using the RUST_LOG environment variable:
RUST_LOG=info,h2=info,hyper_util=info,gcp_auth=info ...
So, for now, the problem doesn't bother me much.
Closes #100 by reducing the log level to
debug
when using theinstrument
attribute macro. This will avoid polluting theINFO
logs of downstream users with calls togcp_auth
unless they intentionally turn on thedebug
logging levels.