StatsD Backends

StatsD isn't just for graphite anymore.
You should be using StatsD for your metrics collection, and with alternative backends you can send your metrics to your system of choice.

Transcript

1. StatsD Backends It’s not just for Graphite Friday, November 2, 12
2. You know StatsD right? • Originally by Etsy • https://github.com/etsy/statsd Friday, November 2, 12
3. How about Graphite? • Originally by Orbitz • https://github.com/ graphite-project Friday, November 2, 12
4. Graphite is sweet! • It’s a great tool for the tool belt. • It’s not for everyone though. • Non-”standard” storage format • have to host a “python app” Friday, November 2, 12
5. StatsD backends FTW! • Supports sending to a single or multiple backends. • This may or may not include graphite. Friday, November 2, 12
6. Builtin Backends • Out of the box StatsD supports: • Graphite (of course) • Console for debugging/troubleshooting • Repeater for relaying StatsD packets Friday, November 2, 12
7. Third Party Backends Most found : https://github.com/etsy/statsd/wiki/Backends • amqp-backend • ganglia-backend • librato-backend • socket.io-backend • statsd-backend • mongo-backend • datadog-backend • monitis-backend • instrumental backend • hosted graphite backend • statsd aggregation backend • zabbix-backend • mysql-backend Friday, November 2, 12
8. Don’t see what you like? • creating a custom backend is easy. • the repeater makes it easy to experiment. Friday, November 2, 12
9. Just got easier • Previously Backends calculated data. • Pull request in to move calculations out of backends. • Simplifies backends even more. Friday, November 2, 12
10. The Moral is? • StatsD and StatsD protocol work great • Do : Extend and Improve StatsD • Do : Use StatsD with additional backends • Don’t : reinvent the wheel • Don’t : make your app send metrics to separate places when StatsD can. Friday, November 2, 12
11. Thanks! • Dan Rowe • @draco2002 • drowe@wayfair.com • https://github.com/draco2003 Friday, November 2, 12