Global tracing_subscriber-based logging (probably) has no way to filter based on arti-client instance
So in practice this probably doesn't matter, 'real' applications should only have 1 arti-client instance in-proc so ordinary usage can isolate the arti-client logs via something like this (from onion-masq according to @ahf):
FmtSubscriber::builder()
.with_env_filter("info,smoltcp=trace,onion_tunnel=trace,arti_client=debug,tor_chanmgr=debug,tor_proto=debug")
.init();
The problem is that in my gosling tests I often have multiple 'TorProvider' instances living in the same process to test things using actual tor connections (ie Alice on TorProvider A and Beth on TorProvider B). This sort of setup coupled with the global tracing based logging will make exposing TorLog events on these TorProviders (probably) impossible to do since we don't know which arti-client instance a trace event is supposed to be routed to/associated with.
It would be nice to somehow consume a stream of log events (like BootstrapStatus on TorClient) that are explicitly associated with an arti-client instance, or to somehow be able to filter the tracing events based on some sort of unique-id tag or something associated with an arti-client instancce (don't know what is best or idiomatic in Rust here).