dd-trace-rb icon indicating copy to clipboard operation
dd-trace-rb copied to clipboard

Failed to report profiling data, connection closed before message completed

Open ganey opened this issue 8 months ago • 3 comments

Current behaviour Intermittent errors sending traces, unsure how to debug further

E, [2024-06-13T08:29:54.066769 #28] ERROR -- ddtrace: [ddtrace] (/usr/local/bundle/gems/ddtrace-1.22.0/lib/datadog/profiling/http_transport.rb:62:in `export') Failed to report profiling data ({:agent=>"unix:///var/run/datadog/apm.socket"}): failed ddog_prof_Exporter_send: connection closed before message completed

Expected behaviour no error sending trace

Steps to reproduce Unsure, happens randomly across cluster and different pods

How does datadog help you?

Environment

  • datadog version: 1.7.45
  • Configuration block (Datadog.configure ...):
Datadog.configure do |c|
  c.tracing.instrument(:sneakers, service_name: 'workers')
  c.tracing.instrument(:active_record, describes: :primary, service_name: 'postgres')

  c.tracing.instrument(:delayed_job, service_name: 'workers')
  c.tracing.instrument(:active_job, service_name: 'workers')
end
  • Ruby version: 3.2.4
  • Operating system: Kube pod for docker image: ruby:3.2.4-slim-bullseye
  • Relevant library versions:
  • ddtrace 1.22.0 (also tried 1.23.1)

  • Using volume mounted socket, most traces are getting through

  • ddagent image: gcr.io/datadoghq/agent:7.48.1

  • env vars: DD_STATSD_SOCKET_PATH : /var/run/datadog/dsd.socket DD_TRACE_AGENT_URL : unix:///var/run/datadog/apm.socket DD_VERSION :1.7.45

ganey avatar Jun 13 '24 10:06 ganey