Open sergimola opened 1 week ago
Yes I already seen this behavior when operation is so fast that the nodejs engine hasn't been able to process the sending of the trace in the right order. Unfortunately I don't think it can be fixed on this library side, maybe upgrading OTEL dependencies should avoid it...
Sometimes spans do not follow the structure according to the actual execution of the flow.
Here's a simple example:
Correct one:
Wrong one:
It doesn't happen only on this one, but it happens in general