-
Notifications
You must be signed in to change notification settings - Fork 183
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 opentracing to opentelemetry #382
Comments
👋 (I am one of the maintainers of OpenTelemetry).
Shim is aimed at users who want to use OTLP protocol while the code is still instrumented with OpenTracing and plan for incremental migration in large codebases. I looked at |
Actually, one of my targets for |
Hi @srikanthccv .. if we start using opentelemetry that would be manual instrumentation.. right? since currently it doesnt support automatic instrumentation for faust. My question in other thread was, do we have any method available which can be used as decorator over to span child traces for the same. any lead on this? |
The
opentracing
project is deprecated in favor ofopentelemetry
. Due to ongoing flaws withopentracing
, we have had difficulty troubleshooting particular bugs that rely on the usage ofopentracing.Span
objects.We will need to miigrate
opentracing
usage over toopentelemetry
as documented in https://opentelemetry-python.readthedocs.io/en/stable/shim/opentracing_shim/opentracing_shim.html.The text was updated successfully, but these errors were encountered: