-
Notifications
You must be signed in to change notification settings - Fork 568
Set the correct SpanContext in continue_trace #3475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
❌ 3863 Tests Failed:
View the top 3 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
2f4e723 to
d037a10
Compare
|
working distributed trace tested with |
d037a10 to
a01604e
Compare
sentrivana
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻 👍🏻 👍🏻 lgtm
|
|
||
| def start_span(self, span=None, custom_sampling_context=None, **kwargs): | ||
| # type: (Optional[POTelSpan], Optional[SamplingContext], Any) -> POTelSpan | ||
| # TODO-neel-potel ideally want to remove the span argument, discuss with ivana |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the only use for this was using the Transaction from continue_trace, let's get rid of the arg
a01604e to
35e146c
Compare
35e146c to
0082dd9
Compare


This commit makes incoming distributed tracing work and finishes implementing
continue_tracestart_spantoPOTelScopefor now that is a simplified version of the original that just creates aPOTelSpancontinue_tracenow adds a fake remoteNonRecordingSpanwith the correcttrace_id,parent_span_idandparent_sampledfields taken from thePropagationContexttrace_idandspan_idproperties onPOTelSpancloses #3476