Skip to content

OpenTracing Shim: Allow invalid but sampled SpanContext to be returned. - #3471

Merged
carlosalberto merged 14 commits into
open-telemetry:mainfrom
carlosalberto:ot-support-jaeger-debug
Aug 10, 2023
Merged

carlosalberto merged 14 commits into
open-telemetry:mainfrom
carlosalberto:ot-support-jaeger-debug

Conversation

@carlosalberto

Copy link
Copy Markdown
Contributor

This is done to support the jaeger-debug-id functionality, which allows invalid SpanContext with debug information to be propagated.

This came up through an issue in Java: open-telemetry/opentelemetry-java#5339

@yurishkuro please review ;)

This is done to support the jaeger-debug-id functionality,
which allows invalid SpanContext with debug information to
be propagated.
@carlosalberto
carlosalberto requested review from a team May 4, 2023 13:39
@carlosalberto

Copy link
Copy Markdown
Contributor Author

Ping @yurishkuro

@yurishkuro yurishkuro left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I would like to see a reference implementation first. This could mean much larger changes to the SDK implementation, eg handling parent context that is sampled but doesn't have a trace id. Also, the current SDK span context does not have a place to store debug-id. The ticket mentions trace state, but it would cause the value to propagate.

@Oberon00

Oberon00 commented May 9, 2023 •

Copy link
Copy Markdown
Member

Most likely, this will not be implementable as many SDKs will normalize any invalid SpanContext to the completely empty one, losing the sampling bit: #753

Tangentially related also #2176

@yurishkuro

Copy link
Copy Markdown
Member

I do think we should implement & support this. This was quite a common debugging workflow at Uber with Jaeger SDK. But my objection was to starting with changing the spec without having an implementation and full understanding what else needs to change in the SDK.

@carlosalberto

Copy link
Copy Markdown
Contributor Author

@yurishkuro So https://github.com/open-telemetry/opentelemetry-java/pull/5380/files has the changes we would need for Java, plus some simulation of how this could be done. I'm guessing you want a little more 'complete'?

cc @ChenX1993

@yurishkuro

Copy link
Copy Markdown
Member

Left some comments in the PR - would like it to be a bit cleaner, but looks promising.

@github-actions

Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions

github-actions Bot commented Jun 8, 2023

Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions

Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions Bot added the Stale label Jun 21, 2023
@github-actions

github-actions Bot commented Jul 5, 2023

Copy link
Copy Markdown

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions Bot closed this Jul 5, 2023
@carlosalberto carlosalberto reopened this Jul 5, 2023
@github-actions

Copy link
Copy Markdown

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions Bot closed this Jul 13, 2023
@carlosalberto carlosalberto reopened this Jul 13, 2023
@github-actions

Copy link
Copy Markdown

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions Bot closed this Jul 26, 2023
@carlosalberto carlosalberto reopened this Jul 26, 2023
@carlosalberto

Copy link
Copy Markdown
Contributor Author

@yurishkuro While we iterate on the details of the related PR, should we get this PR merged? Anything else you'd like me to clean up?

@github-actions github-actions Bot removed the Stale label Jul 29, 2023
@github-actions

github-actions Bot commented Aug 6, 2023

Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions Bot added the Stale label Aug 6, 2023
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
@carlosalberto

Copy link
Copy Markdown
Contributor Author

@MrAlias does the current language (null or empty value being returned) is fine with you?

@github-actions github-actions Bot removed the Stale label Aug 8, 2023
@carlosalberto

Copy link
Copy Markdown
Contributor Author

Merging as we use the suggested "null or empty" statement as recommended.

@carlosalberto
carlosalberto merged commit b9c8a02 into open-telemetry:main Aug 10, 2023
@carlosalberto
carlosalberto deleted the ot-support-jaeger-debug branch August 10, 2023 16:10
carlosalberto added a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
…d. (open-telemetry#3471)

This is done to support the `jaeger-debug-id` functionality, which
allows invalid SpanContext with debug information to be propagated.

This came up through an issue in Java:
open-telemetry/opentelemetry-java#5339
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants