Investigate the use of tokio-trace for internal Supervisor Logging

[christophermaier]

tokio-trace is a (very) new library for scoped, structured logging and diagnostics in async programs. Despite its name, it is not Tokio-specific, but does serve an important need in the Tokio ecosystem (namely, helping figure out what's going on in heavily-futures-based systems where tasks can get passed around to many threads in the course of execution).

This talk on Youtube provides a useful overview.

The ability to add scoped, structured logs will be a huge win (I experimented briefly with log_mdc for this, but it's not a great fit with futures... it's really more for situations where you have a dedicated thread-per-task structure). Being able to correlate information across the entire execution of a future is also going to be incredibly useful for debugging, monitoring, etc.

Once we have consolidated all our output under the common log interface (see #6584), we could begin to experiment with tokio-trace. I think there may be some "glue" that will need to be written to help make log4rs be an output destination for tokio-trace, so that will need to be investigated as well.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.