You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm implmenting spans to track progress and I think when callback is triggered from outside of scope we loose span hierarcy.
My current hack is to create tracer.startSpan early, but then I can't really see actual call runtime.
Or create some sort ref like SpanRef which can be still ref.startActiveSpan() to keep span ref in scope.
Describe alternatives you've considered
Create tracer.startSpan early, but this loses actualy time used on callback.
Tested also binding callback in many different ways, but this just looses tracer hierarcy if not created before actual call.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm implmenting spans to track progress and I think when callback is triggered from outside of scope we loose span hierarcy.
My current hack is to create tracer.startSpan early, but then I can't really see actual call runtime.
Describe the solution you'd like
Or alteratively, ability to make manual link to parent Span when starting new span.
Or create some sort ref like
SpanRef
which can be stillref.startActiveSpan()
to keep span ref in scope.Describe alternatives you've considered
Create tracer.startSpan early, but this loses actualy time used on callback.
Tested also binding callback in many different ways, but this just looses tracer hierarcy if not created before actual call.
The text was updated successfully, but these errors were encountered: