Activations of remote spans wil lbe effectively ignored:
If a remote span is activated as first span on a thread (typical case), it won't start a profiling session. Only when an actual server-span (child of the remote span) is started, the profiling will be started.
If a remote span is activated while a profiling session is already active (=it replace a local span), this activation is effectively ignored. This means inferred spans on the given thread will continue to be children of the previously active span.
@AlexanderWert you observed some strange behaviour of invalid parent/child relationships with a GRPC use-case. Would be great if you find the time to check with the snapshot from this PR if it fixes the issue.
Closes #250.
Activations of remote spans wil lbe effectively ignored:
If a remote span is activated while a profiling session is already active (=it replace a local span), this activation is effectively ignored. This means inferred spans on the given thread will continue to be children of the previously active span.
@AlexanderWert you observed some strange behaviour of invalid parent/child relationships with a GRPC use-case. Would be great if you find the time to check with the snapshot from this PR if it fixes the issue.