9 engineers on Hacker News describe using StatsD first-hand: 5 endorse it, 0 regret it, 0 are mixed.
“felt a push model worked better for us”
endorse · production · danpalmer · 2023-07-05 · source ↗ · wrong label?“we started out using simple StatsD messages that are a few bytes long, easy to implement, easy to debug, and quick.”
endorse · production · lxe · 2020-12-30 · source ↗ · wrong label?“It's been very useful for troubleshooting odd behaviors and correlating events across the platform.”
endorse · production · hoop · 2012-11-08 · source ↗ · wrong label?“Yes, at IFTTT we use this. I've been pleasantly surprised at the amount of traffic statsd can handle, even without sampling.”
endorse · production · jashmenn · 2012-11-08 · source ↗ · wrong label?“I haven't had a chance to use it in production extensively, but I tested it a bit and liked it very much.”
endorse · personal · StavrosK · 2012-08-06 · source ↗ · wrong label?“When we migrated from StatsD that became a problem.”
neutral · production · hinkley · 2024-04-26 · source ↗ · wrong label?“This is how I scaled StatsD at SoundCloud (without having to change client code) before we switched to Prometheus”
neutral · production · jrv · 2015-06-15 · source ↗ · wrong label?“even just for pushing stats to statsd it was not performing well enough”
neutral · production · benmmurphy · 2013-08-27 · source ↗ · wrong label?“We use StatsD at SeatGeek (any at my previous job as well) to track as much as possible.”
neutral · production · philipcristiano · 2012-11-08 · source ↗ · wrong label?