I filed https://github.com/sebasmagri/env_logger/issues/122 a few minutes ago, then I noticed that pretty_env_logger supports timestamps and that adding milliseconds would be easy over here. This is obviously an opinionated pull request, submitted humbly. :)

I also replaced the space with T. I like it that way because then the timestamp is one field if you're parsing with awk or something like that, and it's iso8601-preferred. But I'm willing to revert that part of the change if it's a deal breaker.

This PR updates env-logger to version 0.9 since it's been out for a few months now (and 0.8 even longer).

The only upstream breaking change is the MSRV being increased to 1.41. However, while I don't see a MSRV for pretty_env_logger, its doubtful it will break any users as Debian stable ships a minimum of 1.41.1 and the majority of users are on newer compiler versions.

Closes https://github.com/seanmonstar/pretty-env-logger/issues/50

I'm using pretty-env-logger (through quicli) for a long-lived daemon, and I would need to dynamically change its log level at runtime (my daemon sends logs via network, and something "in the cloud" may ask it to log more or less).
How is it possible to do that ? Or if not possible currently, would it be possible as a feature ?

Hi,

During work on https://github.com/rust-lang-nursery/log/ documentation, we wanted to add link to this crate as one of the most popular implementations. Unfortunately it has no documentation. Currently it does not seam to be intended for 3'rd party adoption. Would you be open to adding few sentences to docs?

Please refer to: https://github.com/rust-lang-nursery/log/pull/188/commits/dbd3c44bc0b030c3b928635de0e059f55e8ae67b#r119920413

I like the formatted logger but I also want line number and file name. Do you think this functionality makes sense?

If so, I can add this meta builder and implement the other builders based on this current one.

This is just a PR to show you my intention.

Prints something like this:

2020-06-07T19:02:47.817Z common_handlers.rs:69 INFO server::common_handlers > Received request..

@seanmonstar I just created a fork of your logger to expose the env_logger::Builder - I like the formatting but was needing more control over the logger... I also added some more examples.

If you are interested in merging the changes I can send you a pull request for review.

It appears that there are a bunch of staled issues and PRs, if it's not maintained anymore, the repository should be archived or transferred to someone, avoiding unnecessary creation of PRs and issues.

the env_logger package provides env_logger::builder().is_test(true).try_init() which allows logs to be captured. It would be nice to expose this in this crate as well.

The github metadata (the text at the top of the repo, above the readme, above the file list on the repo homepage) links to https://crates.io/pretty_env_logger, which is not a valid link; it should be https://crates.io/crates/pretty_env_logger.

formatted_builder cannot error; it does not call anything which returns an error. The documentation looks like a copy-paste error.

This will be an incompatible public API change, which might not be wanted. If not, I still suggest fixing the documentation, perhaps to:

This function fails only if there's a problem constructing the builder. Setting the logger is not attempted.

The function signature is pretty useless anyway, even given future errors coming into existence, as it's unlikely the builder would ever return a SetLoggerError.

fixes https://github.com/seanmonstar/pretty-env-logger/issues/2

Unfortunately I did not know how to add colored text example within rustdoc and README.md without embedding image.

Is it possible to disable the automatic alignment of log messages? This often causes huge space as soon as there is one significantly longer target, so I would rather completely disable it and print > message here directly after the target with only a single space in between.

#5 is still open, but I don't know whether it refers to this or something different.

I tried using formatted_builder() and now the RUST_LOG env var seems to be completely ignored. Is this function working?

I also saw these comments implying that the function is broken: https://github.com/seanmonstar/pretty-env-logger/issues/41#issuecomment-682032429 https://github.com/seanmonstar/pretty-env-logger/issues/20#issuecomment-682038868

Re-export the atty, humantime and regex features. Some time-related features are disabled without humantime.

I did not make termcolor optional because it seemed too interleaved with pretty_env_logger's code, and because I'm not sure it would still justify the name without this. (-:

The biggest gain is eliminating the the regex feature/dependency, which I noticed was adding 1.1MB to my stripped release build .so file.

The default behavior remains the same with everything enabled.

Executing this code

use log::{trace, debug, info, warn, error};

fn main() {
    pretty_env_logger::formatted_builder().init();

    trace!("a trace example");
    debug!("deboogging");
    info!("such information");
    warn!("o_O");
    error!("boom");
}

with

RUST_LOG=trace cargo run

prints

 ERROR terminal_image > boom

and this is quite confusing, because I expected it to print all log levels (it ignores the environment variable).