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

[dogstatsd] fix server address when non_local_traffic is passed #2691

Merged
merged 1 commit into from Jul 25, 2016

Conversation

masci
Copy link
Contributor

@masci masci commented Jul 20, 2016

We used to pass an empty string '' meaning any available interface when non_local_traffic is present in the config file.

This doesn't play well with the new code since we now use a unique, fullstack socket so we explicitly set the IPv4 meta address 0.0.0.0 for retro compat.

This leaves an open issue: it's not possible to start the agent with non_local_traffic on an IPv6 only environment. For standalone Dogstatsd instances this is not a real issue, one can pass :: as bind_host.

@remh
Copy link
Contributor

remh commented Jul 20, 2016

Looks good to me

@masci masci merged commit 7b25511 into master Jul 25, 2016
@masci masci deleted the massi/dogstatsd-non-local branch July 25, 2016 08:41
degemer added a commit that referenced this pull request Jul 28, 2016
* master: (119 commits)
  [core] remove noisy logs (#2715)
  run multiple instances of pylint (#2716)
  [packaging] Release 5.8.5 (#2712)
  [changelog][5.8.5] Add notes on packaging changes (#2710)
  [changelog] Update 5.8.5 with python upgrade
  be more specific when logging ssh errors (#2708)
  [marathon] allow base_url with path (#2620)
  [changelog] Update 5.8.5
  add issue and pr templates
  [sdk] minor tweaks - sdk env detection, check location (#2694)
  [http_check] log exceptions 🔊
  use 0.0.0.0 as server address when non_local_traffic is passed (#2691)
  [elastic] tag stats metric with the node name 🏷 (#2696)
  [openstack] moving proxy logic to AgentCheck, for maintainability. Fixing typos.
  [changelog] 5.8.5 draft
  [tests] lower flakiness of test_no_parallelism (#2690)
  [core] don't use docker hostname if it's a EC2 one (#2661)
  [haproxy] Fix `KeyError` when an unknown status is found (#2681)
  [changelog] Fix md links
  [jenkins] Deprecate check (#2688)
  ...
@olivielpeau olivielpeau added this to the 5.9.0 milestone Jul 29, 2016
@bchen421
Copy link

What about multi-home systems that are on many networks? We want to explicitly set bind_host to listen on trusted networks and allow non_local_traffic, but now we have to work around this by using iptables or some set of security group rules. Shouldn't a setting called bind_host actually set the bind_host? We upgraded to agent 5.10 and was hit with this unpleasant surprise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants