-
Notifications
You must be signed in to change notification settings - Fork 377
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
gem doesn't honor DISABLE_DATADOG_AGENT env var #1130
Comments
@breathe thanks for reaching out. So, I wasn't familiar with that env var off the top of my head but, looking into it, i believe that
from: https://docs.datadoghq.com/agent/basic_agent_usage/heroku/#configuration The datadog-agent is the daemon that this If you want to disable the
from: https://github.com/DataDog/dd-trace-rb/blob/master/docs/GettingStarted.md#tracer-settings We recently merged in support for an env var to disable the ruby tracing client (
Does that help? Also, always feel free to reach out to support if there's more detailed environment specific information or logs that may contain sensitive information which need to be shared. |
awesome thank you @ericmustin ! I'm using code like this to ensure gem honors both these env vars and seems to work in our environments
Please feel free to close this ticket now or close later when the support for Appreciate the help! |
We'll ship |
We've just released 0.39.0, which adds support for the |
We get extraneous output when running our ruby code in an environment with DISABLE_DATADOG_AGENT=true.
The agent processes won't be started (due to the presence of the env var) - but the gem still tries to log to the non-running agents and produces extraneous error log output ...
The text was updated successfully, but these errors were encountered: