-
Notifications
You must be signed in to change notification settings - Fork 303
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
Why do we try to read /etc/dd-agent/datadog.conf
?
#176
Comments
Thanks for reporting @tgwizard. The idea is to grab, if defined, the However, I realize this is not a good idea:
|
Is fix for this issue planned for release? |
Apologies for the really long delay in updating this thread. We've taken care of this in #428 (downgrade to warning and add an option |
Closing this issue now, see @dabcoder's comment above on how to get rid of these errors. |
Why does the
datadog
library try to read the Datadog Agent config on/etc/dd-agent/datadog.conf
? It seems to only be used indatadogpy/datadog/util/hostname.py
Line 54 in 969c703
To be able to read the config file, the service running the
datadog
library must have read privileges for that file. However, the default settings from the datadog cookbook marks the config file as owned bydd-agent:root
, with permissions0640
. We don't want to run our services as either thedd-agent
user or a user in theroot
group, and the datadog cookbook doesn't allow us to change the permissions.It all works fine even without the read permissions -
datadog
defaults to parsinghostname -f
. However, as of #161, we get a log line likeevery time we start our services.
Why do we need to read the hostname from the config file - isn't
hostname -f
good enough? Or do people often have custom hostnames in the datadog agent config file? How do people solve the config file permission issue?The text was updated successfully, but these errors were encountered: