Bug Report

I just lost decent amount of time debugging a problem that turned out to be tracing-subscriber logging to stdout which was overlooked during refactoring. This is a second, if not third time in the recent past where I've dealt with wrong defaults in tracing-subscriber creating issues.

I don't recall ever wanting to get my log output to stdout, and as far as I can tell logging to stderr is a well estabilished convention, to separate main program output from diagnostics.

At very least env_logger defaults to stderr , so does e.g. slog-term, so do most logging libraries I've used and can remember.

Is there any reason why tokio-subscriber would go against this convention?

I realize that at this point reverting the default might be a hassle, but just want to point it out and ask.