Yes. Sorry for it not being clear. But yes, each message event has child span to the parent. This helps find issues on individual messages related to a connection.
The problem here is that you don't see the full trace until after the connection is closed.
I should also state that this only makes sense when the trace attributes are relatively light in count. Else, the memory footprint of this can get uncomfortable. 😅
Another approach (I haven't tried) is running the context response for a child span as a individual forked process, but using the original trace id as a context id.
You get the message event span, but relationship is still identifiable. Though not in a pretty flame. 😅
Comments
Downside, you see a parent for like 600s with the child spans being relatively short.
The problem here is that you don't see the full trace until after the connection is closed.
You get the message event span, but relationship is still identifiable. Though not in a pretty flame. 😅