Quinn

> If we have the fields on the same line as the span, would that be their values at span entry? I'm thinking we would have both on the same...

> I'd also perhaps suggest (after playing around a little) that a "record update" tree node might be useful. Selfishly for my project I need to know when `Span::record` is...

> Sounds good. I'm asking if we should report the field values when the span is entered or what the field values are by the time the span is exited....

Let me know if you need help with anything, I've spent a lot of time looking through tracing and tracing-subscriber docs...

So just to clarify, you're trying to send an event when you record, but not necessarily print out changed fields when a span closes right? If so then what you...

This look okay? https://github.com/QnnOkabayashi/tracing-forest/pull/35 After this I'll update to 0.1.6.

Hi yaleman! If you're still stuck on this, I think what you want is the [`map_receiver`](https://docs.rs/tracing-forest/latest/tracing_forest/runtime/struct.Builder.html#method.map_receiver) method. In the closure you would provide it, you can call the [`writer`](https://docs.rs/tracing-forest/latest/tracing_forest/printer/struct.Printer.html#method.writer) method...

After some thought, I think it would be a good idea to put it behind a feature flag like `watch_span_fields`. My reasoning for this is that I realized after creating...

Although a more scalable solution would be my original idea, which is to make doing certain things on `OpenedSpan`s and constructing `Event`s part of a public API. Then these extra...

Can you expand on what scenarios this could occur in (i.e. socket listeners)? I want to better understand why this would ever happen. I'm thinking this is more application specific....