-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Unable to integrate Uvicorn (multiple workers) to SigNoz. #1113
Comments
Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines. |
@srikanthccv do you have insights on this? |
@nitin1993915 Which version of SDK are you using? Unlike gunicorn, uvicorn doesn't have any hooks that can be used to instantiate new span processor for each worker https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples/fork-process-model. The newer version of sdk attempt to fix this to certain extent but there might be some limitation with uvicorn. |
@nitin1993915 Just checking if you are still facing this issue or this is solved. Please update here accordngly |
Hi @pranay01 I am still facing this same when using multiple workers. With single worker, it works fine. |
You can get it to work using gunicorn + uvicorn.workers.UvicornWorker class but the uvicorn is directly not supported. Please follow up on the upstream repo for any updates open-telemetry/opentelemetry-python-contrib#385. |
Bug description
*Below mentioned Docker CMDs work with single uvicorn worker to get the app traces but does not work with multiple uvicorn workers
["opentelemetry-instrument",
"uvicorn", "app:app", "--host", "0.0.0.0", "--port", "8000"]-- worked
["opentelemetry-instrument",
"uvicorn", "app:app", "--host", "0.0.0.0", "--port", "8000", "--workers", `"2"]-- did not work
*
Expected behavior
Should be able to check the traces on UI with multiple unicorn workers
The text was updated successfully, but these errors were encountered: