3 ms·
Yeah this has come up and it's reasonable, although it's a tricky/laborious migration in practice given a wide variety of things emitting stats. The statsd des
by mcfunley 11y ago
Yeah this has come up and it's reasonable, although it's a tricky/laborious migration in practice given a wide variety of things emitting stats.
The statsd design choices here are mostly explained by the fact that Etsy uses it to collect from PHP. PHP doesn't afford a great way to aggregate in the client. (These are design choices that serve PHP well systemically, although it's limiting here.)
- bbrazil 11y agoI hadn't realised the PHP link, things make more sense now. You're getting into IPC then, which is a fun topic alright e.g. https://github.com/prometheus/client_ruby/issues/9 https://github.com/prometheus/client_ruby/issues/9 and https://github.com/prometheus/client_python/issues/30 https://github.com/prometheus/client_python/issues/30
- jrv 11y agoThis is how I scaled StatsD at SoundCloud (without having to change client code) before we switched to Prometheus: http://stackoverflow.com/questions/12871642/scaling-statsd-with-multiple-servers http://stackoverflow.com/questions/12871642/scaling-statsd-w... (the first answer)
- _wmd 11y agoNot suggesting it's a good idea, but the PHP standard library gives you enough tools (shmop) to allow a straight port of something like https://github.com/schmichael/mmstats https://github.com/schmichael/mmstats