DNS queries for the statsd host repeated for each socket.sendto call about logster

[elukey]

This might not really be possible since the suggested use is in a crontab, I was convinced that there were different ways of tailing a log. Sorry for the spam! :)

[elukey]

Re-thinking about this issue made me realize that there is a small improvement that is possible for https://github.com/etsy/logster/blob/master/logster/outputs/statsd.py#L23-L36, namely a gethostbyname before the for loop in order to pass an IP address to the sendto() rather than a domain, triggering a lot less DNS queries for each run. Does it make sense?

[benburry]

Are these DNS queries expensive in your infrastructure? I would have expected them to be answered by the local DNS cache, and so result in very little impact to actual performance

[elukey]

Hi! We don't have local resolvers on the hosts but only "remote" resolvers behind a LVS load balancer. This is not affecting heavily our infrastructure but I wanted to reduce (what I think is) unnecessary traffic. In this case resolving the domain right before the loop doesn't seem a big problem and instantly reduces traffic towards our resolvers.