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
👋 Hello, I was wondering if there was any way you'd be open to allowing a span to be created with an already existing SpanContext? I have a unique use case where I need to save an in-progress span and ship it out of memory, and then later reload it into memory and finish the span. I was wondering if you'd be open to supporting this feature in the lightstep go client?
The text was updated successfully, but these errors were encountered:
dm03514
changed the title
Support Exporting SpanContext and initializing Span with A given Context
Support for Initializing Span with A given Context
Oct 31, 2019
dm03514
changed the title
Support for Initializing Span with A given Context
Support for Initializing Span with a Previously Started Context
Oct 31, 2019
👋 Hello, I was wondering if there was any way you'd be open to allowing a span to be created with an already existing SpanContext? I have a unique use case where I need to save an in-progress span and ship it out of memory, and then later reload it into memory and finish the span. I was wondering if you'd be open to supporting this feature in the lightstep go client?
I was able to add support for this in the jaeger client, and was hoping to use the same functionality with LightStep:
jaegertracing/jaeger-client-go#397
The strategy we took for jaeger was to add a SelfRef type that bhs proposed:
opentracing/specification#81 (comment)
If you're interested I would be happy to contribute this!
I was imagining the same API and approach as the jaeger library:
Which would require:
SelfRefType
:newSpan
to check forSelfRefType
and setsp.raw.Context
equal to the provided context reference context:I think this is everything needed to then export a context:
Then starting a span with a previously started context:
I really appreciate your time! Thank you
Danny
The text was updated successfully, but these errors were encountered: