-
Notifications
You must be signed in to change notification settings - Fork 477
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
migrate from jaeger-sdk to otel-sdk #2224
Comments
Yes! I agree we need to move forward to the OTEL clients. At one point there was an attempt to do this: Line 230 in 944e5ae
but for some reason context was not propagating between services and the work got shelved. If you, or anyone else, would like to take up figuring out the last bits we would be grateful. |
I would like to look at it more closely. But I will not be able to do that in the next weeks. 😔 |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. |
Is your feature request related to a problem? Please describe.
Currently all tempo components are instrumented using the Jaeger-SDK that is at end of life. This requires additional configurations to collect those traces and might leads to future security issues.
Describe the solution you'd like
Migrate to OTEL-sdk. ^^
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: