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

Migrate from opentracing to opentelemetry #382

Open
wbarnha opened this issue Oct 12, 2022 · 3 comments
Open

Migrate from opentracing to opentelemetry #382

wbarnha opened this issue Oct 12, 2022 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@wbarnha
Copy link
Member

wbarnha commented Oct 12, 2022

The opentracing project is deprecated in favor of opentelemetry. Due to ongoing flaws with opentracing, we have had difficulty troubleshooting particular bugs that rely on the usage of opentracing.Span objects.

We will need to miigrate opentracing usage over to opentelemetry as documented in https://opentelemetry-python.readthedocs.io/en/stable/shim/opentracing_shim/opentracing_shim.html.

@srikanthccv
Copy link

👋 (I am one of the maintainers of OpenTelemetry).

We will need to miigrate opentracing usage over to opentelemetry as documented in https://opentelemetry-python.readthedocs.io/en/stable/shim/opentracing_shim/opentracing_shim.html.

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 opentracing usage Faust codebase. I think you are better off truly migrating over to OpenTelemetry by directly instrumenting with opentelemetry-api. Let us know if you need any clarification and help with this.

@lqhuang
Copy link

lqhuang commented Dec 16, 2022

Actually, one of my targets for mode-ng is to integrate OpenTelemetry protocol. Of course, long way to go 😭

@Chiraguthra
Copy link

👋 (I am one of the maintainers of OpenTelemetry).

We will need to miigrate opentracing usage over to opentelemetry as documented in https://opentelemetry-python.readthedocs.io/en/stable/shim/opentracing_shim/opentracing_shim.html.

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 opentracing usage Faust codebase. I think you are better off truly migrating over to OpenTelemetry by directly instrumenting with opentelemetry-api. Let us know if you need any clarification and help with this.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants