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
in kubernetes, constantly seeing these errors for our golang services when tracing is enabled:
Describe what you expected:
while the apm functionality is still working for these services, this error shouldnt be present. it seems while its still sending traces over unix socket, the tracer is still trying to talk to the datadog agent over http port for some reason.
i cannot tell you what the bug is, its not our agent. i can only tell you what we are observing. and we are seeing this issue for every single Golang service using datadog agent.
@pdeva I didn't ask you that. Sorry for that. What you are observing doesn't match with my first insights. I'll try to reproduce it with a realistic setup.
Version of dd-trace-go
1.62.0
Describe what happened:
in kubernetes, constantly seeing these errors for our golang services when tracing is enabled:
Describe what you expected:
while the apm functionality is still working for these services, this error shouldnt be present. it seems while its still sending traces over unix socket, the tracer is still trying to talk to the datadog agent over http port for some reason.
Steps to reproduce the issue:
this is how we init our tracer:
here is the relevant config of the k8s deployment of each of the services:
this is the relevant config of the datadog helm chart:
Additional environment details (Version of Go, Operating System, etc.):
EKS 1.29
Go 1.22.1
The text was updated successfully, but these errors were encountered: