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

[util] do not read hostname from datadog.conf #185

Closed
wants to merge 1 commit into from

Conversation

yannmh
Copy link
Member

@yannmh yannmh commented Jan 23, 2017

To be able to read the datadog.conf Datadog Agent configuration file,
the user must have read privilege to the file (default to 0640 dd-agent:root).

It is also useless: if a datadog.conf file is present on the host, one
can use statsd to have metrics, events... sent with the appropriate
hostname.

Fix #176, #178. Thanks @tgwizard, @donato.

To be able to read the `datadog.conf` Datadog Agent configuration file,
the user must have read privilege to the file (default to `0640
dd-agent:root`).

It is also useless: if a `datadog.conf` file is present on the host, one
can use `statsd` to have metrics, events... sent with the appropriate
hostname.
@yannmh yannmh requested a review from degemer January 23, 2017 20:19
@yannmh yannmh self-assigned this Jan 23, 2017
@yannmh yannmh added this to the 0.16.0 milestone Jan 23, 2017
@donato
Copy link

donato commented Jan 23, 2017

Thanks @yannmh - let me know when I should upgrade and test this out :)

@yannmh yannmh modified the milestones: 1.0.0, 0.16.0 Feb 13, 2017
dmlook pushed a commit to lovepopcards/datadogpy that referenced this pull request Feb 16, 2019
@dabcoder
Copy link
Contributor

We took care of this in #428, rather than fully deprecating this agent config hostname look up, it adds an option to turn this on/off.

@dabcoder dabcoder closed this Oct 28, 2019
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

Successfully merging this pull request may close these issues.

Why do we try to read /etc/dd-agent/datadog.conf?
3 participants