Skip to content
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

Proper scope handling for Resteasy instrumentations. #1442

Merged
merged 2 commits into from
Oct 22, 2020

Conversation

iNikem
Copy link
Contributor

@iNikem iNikem commented Oct 21, 2020

Fixes #1422. This PR solves the original problem with Resteasy. If other JAX-RS client implementations have the same problem, remains to be seen.

Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

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

Nice!

* JAX-RS Client API doesn't define a good point where we can handle connection failures, so we must
* handle these errors at the implementation level.
* Unlike other supported JAX-RS Client implementations, Resteasy's one is very simple and passes
* all requests through single point. Both sync ADN async! This allows for easy instrumentation and
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* all requests through single point. Both sync ADN async! This allows for easy instrumentation and
* all requests through single point. Both sync AND async! This allows for easy instrumentation and

@iNikem iNikem merged commit 6438d1d into open-telemetry:master Oct 22, 2020
@iNikem iNikem deleted the resteasy-scope branch October 24, 2020 07:11
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.

Resteasy client leads to duplicate spanId injections into http headers
3 participants