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.

Sign up for GitHub

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

Jump to bottom

Context keys from instrumentation-api should be bridged #4319

Closed
iNikem opened this issue Oct 7, 2021 · 0 comments · Fixed by #5838
Closed

Context keys from instrumentation-api should be bridged #4319

iNikem opened this issue Oct 7, 2021 · 0 comments · Fixed by #5838
Assignees
@mateuszrzeszutek
Labels
bug Something isn't working

Comments

@iNikem
Copy link
Contributor

iNikem commented Oct 7, 2021

instrumentation-api module can be added to an application classpath, e.g. for library instrumentations. This will result in different ContextKey instances e.g. io.opentelemetry.instrumentation.api.servlet.ServerSpanNaming#CONTEXT_KEY. For them to work correctly with the agent, they probably has to be bridged or something.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mateuszrzeszutek mateuszrzeszutek

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
2 participants
@iNikem @mateuszrzeszutek