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

Add Env var called DD_DOGSTATSD_SOCKET to not conflict with DD_APM_RECEIVER_SOCKET #201

Open
smitthakkar96 opened this issue Jun 9, 2021 · 2 comments

Comments

@smitthakkar96
Copy link

Since the sockets are supported for both StatsD and APM setting DD_AGENT_HOST would break either DogStatd or APM as they both have different paths. As per the helm chart the socket paths are as followed /var/run/datadog/apm.socket and /var/run/datadog/dsd.socket.

@hush-hush
Copy link
Member

HI @smitthakkar96,

Thanks for opening this issue. I'll look into it and sync with the APM team. But adding a new env var sound like a good idea.

@hush-hush
Copy link
Member

There actually is the DD_TRACE_AGENT_URL setting on the trace agent (https://docs.datadoghq.com/tracing/setup_overview/setup/python/?tab=containers). But this is not yet implemented in the Go client. There is a issue open here.

@knusbaum knusbaum changed the title Add Env var called DD_DOGSTATSD_SOCKET to not conflict with DD_APM_RECEIVER_SOCKET proposal: Add Env var called DD_DOGSTATSD_SOCKET to not conflict with DD_APM_RECEIVER_SOCKET Nov 12, 2021
@knusbaum knusbaum changed the title proposal: Add Env var called DD_DOGSTATSD_SOCKET to not conflict with DD_APM_RECEIVER_SOCKET Add Env var called DD_DOGSTATSD_SOCKET to not conflict with DD_APM_RECEIVER_SOCKET Nov 12, 2021
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

2 participants