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

Cannot decode v0.4 traces payload: msgp: too few bytes left to read object #9555

Open
rkdrnf opened this issue Oct 18, 2021 · 4 comments
Open

Comments

@rkdrnf
Copy link

rkdrnf commented Oct 18, 2021

Describe what happened:

Cannot decode v0.4 traces payload: msgp: too few bytes left to read object

Sometimes above error occurs on datadog agent container.
Usually it just works fine without any error.

ERROR:ddtrace.internal.writer:failed to send traces to Datadog Agent at http://datadog-agent:8126: HTTP error status 400, reason Bad Request

ddtrace client error occurs as a result.

Describe what you expected:
There should be no error on both datadog agent container and ddtrace client.

Additional environment details (Operating System, Cloud provider, etc):
Running datadog agent docker image gcr.io/datadoghq/agent:7
AWS ElasticBeanstalk Linux AMI 2 Docker Platform

Client:
Python 3.6
Flask
Running ddtrace with following uwsgi options

enable-threads=true
lazy-apps=true
import=ddtrace.bootstrap.sitecustomize
@florianmutter
Copy link

Did someone find out where this comes from? We also see a lot of the Cannot decode logs but I have no idea which component sends the invalid traces.

@s7an-it
Copy link

s7an-it commented Jan 22, 2023

I get that error on tracerAgent.

@rahul-paigavan
Copy link

Observing similar issue - is there any impact of this on dropped traces/spans??

@peterdeme
Copy link

Anyone figured this one out?

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

No branches or pull requests

5 participants