Use Case
Late spans should be handled correctly by Raw Spans Grouper. Currently, once a trace is emitted, the corresponding entry is deleted from the state store. Any spans received after this will be treated as the first span of a new trace (as there is no entry in the state store) with the traceId of the previously emitted trace. So essentially the application emits multiple traces with the same traceId. This certainly is an edge case but would be nice to be aware of it at least.
Proposal
--
Questions to address (if any)
--
Use Case
Late spans should be handled correctly by Raw Spans Grouper. Currently, once a trace is emitted, the corresponding entry is deleted from the state store. Any spans received after this will be treated as the first span of a new trace (as there is no entry in the state store) with the traceId of the previously emitted trace. So essentially the application emits multiple traces with the same traceId. This certainly is an edge case but would be nice to be aware of it at least.
Proposal
--
Questions to address (if any)
--