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
Describe what happened:
Getting around a million per week, it seems like it's failing to parse, so we're probably missing some traces, but IDK what the payloads are, let me know if you an idea how to provide more debugging info.
yyyy-MM-dd HH:mm:ss UTC | TRACE | ERROR | (pkg/trace/api/api.go:384 in handleTraces) | Cannot decode v0.4 traces payload: msgp: attempted to decode type "array" with method for "str"
E, [yyyy-MM-ddTHH:mm:ss.SSSSSS #[597-32597]] ERROR -- ddtrace: [ddtrace] (/srv/platform/shared/bundle/ruby/2.5.0/gems/ddtrace-0.43.0/lib/ddtrace/transport/http/client.rb:35:in `rescue in send_request') Internal error during HTTP transport request. Cause: Empty input at line 1, column 1 [parse.c:926] in 'msgp: attempted to decode type "array" with method for "str"
Describe what you expected:
No logs about parsing failures.
closing as there is no way to repro, it's old, and mostly because it's probably fixed by DataDog/dd-trace-java#6892 and available in tracer versions >= 1.33
Output of the info page (if this is a bug)
Describe what happened:
Getting around a million per week, it seems like it's failing to parse, so we're probably missing some traces, but IDK what the payloads are, let me know if you an idea how to provide more debugging info.
Describe what you expected:
No logs about parsing failures.
Steps to reproduce the issue:
IDK
Additional environment details (Operating System, Cloud provider, etc):
The text was updated successfully, but these errors were encountered: