`tracing_subscriber` should log to stderr

[mxinden]

Summary

Diagnostics (e.g. logging) should go to stderr. Output of a program should go to stdout.

Expected behavior

tracing_subscriber to log to stderr.

Actual behavior

tracing_subscriber is logging to stdout.

Upstream bug report tokio-rs/tracing#2492

Relevant log output

No response

Possible Solution

One can easily override the default:

    let _ = tracing_subscriber::fmt()
        .with_env_filter(EnvFilter::from_default_env())
        .with_writer(std::io::stderr)
        .try_init();

Initialization of tracing_subscriber is already quite noisy. E.g. it requires 4 lines instead of the 1 line of env_logger. Should we introduce some abstraction?

Version

tracing_subscriber introduced with #4282.

Would you like to work on fixing this bug ?

No

[eserilev]

I'd like to pick this up

[thomaseizinger]

Initialization of tracing_subscriber is already quite noisy. E.g. it requires 4 lines instead of the 1 line of env_logger. Should we introduce some abstraction?

I think that would make sense. We only use this in examples and tests, neither of which get released to crates.io, so we can make a crate in misc/ that is publish = false.

[JacobOgle]

@eserilev still working on this? If not I wouldn't mind taking a look

[eserilev]

@JacobOgle feel free to pick this up if you'd like

[nazreen]

Can I pick this up?

[JacobOgle]

@nazreen go for it! I've been too tied up with school to take a dive into it

[nazreen]

@JacobOgle cool! this will be my first time contributing to this repo. the label getting-started is synonymous with good-first-issue right?

[thomaseizinger]

@JacobOgle cool! this will be my first time contributing to this repo. the label getting-started is synonymous with good-first-issue right?

Yes!

[drHuangMHT]

@nazreen Are you currently working on this? I would like to pick this up if you don't mind.