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

agent6 config: include statsd forward params #408

Merged
merged 1 commit into from
Jul 10, 2018
Merged

agent6 config: include statsd forward params #408

merged 1 commit into from
Jul 10, 2018

Conversation

djova
Copy link

@djova djova commented Mar 8, 2018

statsd_forward_host and statsd_forward_port are supported by agent6 so they should be included in the config file.

`statsd_forward_host` and `statsd_forward_port` are supported by agent6 so they should be included in the config file.
@@ -523,6 +523,8 @@
'dogstatsd_port' => $dogstatsd_port,
'dogstatsd_socket' => $dogstatsd_socket,
'dogstatsd_non_local_traffic' => $non_local_traffic,
'statsd_forward_host' => $statsd_forward_host,
'statsd_forward_port' => $statsd_forward_port,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These parameters can actually be included in the $extra_config hash parameter available for additional options.

Copy link
Author

@djova djova Mar 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, and that's what we're doing now, but then isn't it misleading to have the corresponding parameters for the actual class be ignored with agent6? If the intention is to provide those parameters via extra_config then should the puppet class parameters be removed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's honor this, the deep_merge() should probably be seamless.

It's tough keeping an interface that was defined for agent5 with the new datadog.yaml approach in agent6. But this is a 1-to-1 mapping so no reason not to merge. Sorry we kept it in the backburner for so long.

Thanks.

Copy link
Member

@truthbk truthbk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge!

@@ -523,6 +523,8 @@
'dogstatsd_port' => $dogstatsd_port,
'dogstatsd_socket' => $dogstatsd_socket,
'dogstatsd_non_local_traffic' => $non_local_traffic,
'statsd_forward_host' => $statsd_forward_host,
'statsd_forward_port' => $statsd_forward_port,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's honor this, the deep_merge() should probably be seamless.

It's tough keeping an interface that was defined for agent5 with the new datadog.yaml approach in agent6. But this is a 1-to-1 mapping so no reason not to merge. Sorry we kept it in the backburner for so long.

Thanks.

@truthbk truthbk merged commit fe92088 into DataDog:master Jul 10, 2018
@djova djova deleted the djova/agent6-include-statsd-forward-metrics branch July 10, 2018 17:52
@truthbk truthbk added this to the 2.3.0 milestone Jul 11, 2018
cegeka-jenkins pushed a commit to cegeka/puppet-datadog_agent that referenced this pull request Apr 6, 2020
`statsd_forward_host` and `statsd_forward_port` are supported by agent6 so they should be included in the config file.
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.

2 participants