The with-statsd branch contains a working statsd implementation from one of the early prototypes.
It seems like most of the available statsd clients resolve the name of the statsd server once upon created. We need a client that does the lookup each time the stats are flushed in order to properly handle the dynamic nature of Docker's service/container level DNS.
The with-statsd branch contains a working statsd implementation from one of the early prototypes.
It seems like most of the available statsd clients resolve the name of the statsd server once upon created. We need a client that does the lookup each time the stats are flushed in order to properly handle the dynamic nature of Docker's service/container level DNS.