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

[BUG]:Traces Dropped After 5 Retries When Sending to Local Agent Proxy #12020

Open
ryuichi1208 opened this issue Jan 22, 2025 · 3 comments
Open
Labels

Comments

@ryuichi1208
Copy link

ryuichi1208 commented Jan 22, 2025

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:

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

@ryuichi1208 ryuichi1208 changed the title [BUG]: [BUG]:Traces Dropped After 5 Retries When Sending to Local Agent Proxy Jan 22, 2025
@adilnaimi
Copy link

I have the same issue as well:
Flask socketio application (flask-socketio)
gunicorn + eventlet
Deployed to ECS Fargate
ddtrace==2.19.0

failed to send, dropping 2 traces to intake at http://localhost:8126/evp_proxy/v2/api/v2/llmobs after 5 retries

@Yun-Kim
Copy link
Contributor

Yun-Kim commented Feb 5, 2025

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!

@blimmer
Copy link

blimmer commented Feb 6, 2025

We are getting this on ddtrace==2.20.0 as well. We hadn't seen this on 2.18.0, our previous version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants