Skip to content

Preserve parent-child relationship between OpenTelemetry and OpenTracing spans#924

Merged
codeboten merged 15 commits intoopen-telemetry:masterfrom
ocelotl:issue_161
Aug 14, 2020
Merged

Preserve parent-child relationship between OpenTelemetry and OpenTracing spans#924
codeboten merged 15 commits intoopen-telemetry:masterfrom
ocelotl:issue_161

Conversation

@ocelotl
Copy link
Copy Markdown
Contributor

@ocelotl ocelotl commented Jul 18, 2020

Fixes #161

@ocelotl ocelotl added shim OpenTracing or OpenCensus compatibility ext labels Jul 18, 2020
@ocelotl ocelotl requested a review from a team July 18, 2020 02:46
@ocelotl ocelotl self-assigned this Jul 18, 2020
@ocelotl ocelotl force-pushed the issue_161 branch 4 times, most recently from 812e4bc to 81f12df Compare July 22, 2020 00:16
Copy link
Copy Markdown
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Blocking on my comment, and on #922 merging before this PR.

@ocelotl
Copy link
Copy Markdown
Contributor Author

ocelotl commented Jul 31, 2020

This looks good. Blocking on my comment, and on #922 merging before this PR.

Fixed

ocelotl added 14 commits August 6, 2020 17:22
This uses the OpenTelemetry context management mechanism to store a
ScopeShim object in order to make active return the same object as the
one returned by start_active_span.

WIP: there is one failing test case, apparently the context does not get
cleared before running every test case. This seems related to the order
in which test cases are being run.
This uses the OpenTelemetry context management mechanism to store a
ScopeShim object in order to make active return the same object as the
one returned by start_active_span.

WIP: there is one failing test case, apparently the context does not get
cleared before running every test case. This seems related to the order
in which test cases are being run.
This uses the OpenTelemetry context management mechanism to store a
ScopeShim object in order to make active return the same object as the
one returned by start_active_span.

WIP: there is one failing test case, apparently the context does not get
cleared before running every test case. This seems related to the order
in which test cases are being run.
@codeboten codeboten merged commit 3341a8e into open-telemetry:master Aug 14, 2020
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this pull request Nov 1, 2020
It still falls back to localhost, but if the env var is set, it will use that as the host to send spans to. This prevents end users from writing extra code when the jaeger agent is remote.

Signed-off-by: Naseem <naseem@transit.app>

Co-authored-by: Mayur Kale <mayurkale@google.com>
Co-authored-by: Daniel Dyla <dyladan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

shim OpenTracing or OpenCensus compatibility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle "mixed mode" OT/OTel tracing in OT Bridge

3 participants