What are you trying to achieve?
I am trying to ensure that span ID creation for spans that are dropped or only recorded (but not sampled) is uniform across different language implementations.
Additional context.
As explained in #864 (comment) the spec is silent on what to do for IDs of spans that are not sampled. #998 suggest to reuse the parent-span-id for dropped or use zero if there is none, but use a new span ID for everything else. A simpler alternative would be to simply add the sentence "A new Span ID MUST always be generated, even for dropped spans".
This is not purely an optimization issue, it impacts the observable behavior of the monitored application when the unsampled span is injected (and then potentially used as parent on the other side).
What are you trying to achieve?
I am trying to ensure that span ID creation for spans that are dropped or only recorded (but not sampled) is uniform across different language implementations.
Additional context.
As explained in #864 (comment) the spec is silent on what to do for IDs of spans that are not sampled. #998 suggest to reuse the parent-span-id for dropped or use zero if there is none, but use a new span ID for everything else. A simpler alternative would be to simply add the sentence "A new Span ID MUST always be generated, even for dropped spans".
This is not purely an optimization issue, it impacts the observable behavior of the monitored application when the unsampled span is injected (and then potentially used as parent on the other side).