Show the current span in the console.

[najamelan]

By default, tracing-subscriber shows span information in log events. I am using tracing in a library, so I'm trying to figure out how best to annotate things. I call user supplied code, so I don't necessarily get to put structured data directly on the log events, so a span seemed to be a good way to add information. However, if it doesn't get shown that doesn't work. I personally prefer putting the span information after the message, as it seems more optional.

I suppose fixing #13 would also fix this in a more general but less default way.

[lilyball]

I just tried switching over to tracing-wasm and was very surprised to see that the fields I've added to my spans aren't showing up. That removes most of the utility of my logging. Even without supporting tracing-subscriber's FormatEvent, this crate should at least include span names and fields.

[jquesada2016]

Any update on this? Logging without span information is generally a big problem, as all context to the events are lost.