You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using version 2.19.2, the following error message occurs:
failed to send, dropping 1 traces to intake at http://localhost:8126/evp_proxy/v2/api/v2/llmobs
This issue arises in our application, which is a WebSocket-based service built with gunicorn and uses uvicorn as its worker. The traces fail to be sent to the local agent proxy (http://localhost:8126) after 5 retry attempts, leading to the traces being dropped. However, this issue is limited to traces sent to LLMObs, as traces to other destinations were successfully sent without any issues.
This issue does not occur in versions 2.18.2 or 2.18.0. If you need any additional information to investigate the problem, please let us know. We are happy to provide further details or logs as required.
Operating System
AWS Fargate for Amazon ECS
The text was updated successfully, but these errors were encountered:
Hi @ryuichi1208, thanks for reaching out and apologies for the delayed response.
Can you try upgrading to the latest ddtrace==2.20.0 or ddtrace==2.19.3 and see if this issue persists? I believe this may be related/fixed by #11961 which was merged after ddtrace==2.19.2.
If the issue persists, can you send over your tracer debug logs (DD_TRACE_DEBUG=1) to help us debug the underlying issue? Thanks!
Tracer Version(s)
2.19.2
Python Version(s)
Python 3.11
Pip Version(s)
pip 22.04
Bug Report
When using version 2.19.2, the following error message occurs:
This issue arises in our application, which is a WebSocket-based service built with gunicorn and uses uvicorn as its worker. The traces fail to be sent to the local agent proxy (http://localhost:8126) after 5 retry attempts, leading to the traces being dropped. However, this issue is limited to traces sent to LLMObs, as traces to other destinations were successfully sent without any issues.
This issue does not occur in versions 2.18.2 or 2.18.0. If you need any additional information to investigate the problem, please let us know. We are happy to provide further details or logs as required.
Operating System
AWS Fargate for Amazon ECS
The text was updated successfully, but these errors were encountered: