-
Notifications
You must be signed in to change notification settings - Fork 262
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
agent6 config: include statsd forward params #408
Conversation
`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, |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this 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, |
There was a problem hiding this comment.
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.
`statsd_forward_host` and `statsd_forward_port` are supported by agent6 so they should be included in the config file.
statsd_forward_host
andstatsd_forward_port
are supported by agent6 so they should be included in the config file.