Slide 1

Slide 1 text

StatsD Backends It’s not just for Graphite Friday, November 2, 12

Slide 2

Slide 2 text

You know StatsD right? • Originally by Etsy • https://github.com/etsy/statsd Friday, November 2, 12

Slide 3

Slide 3 text

How about Graphite? • Originally by Orbitz • https://github.com/ graphite-project Friday, November 2, 12

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

StatsD backends FTW! • Supports sending to a single or multiple backends. • This may or may not include graphite. Friday, November 2, 12

Slide 6

Slide 6 text

Builtin Backends • Out of the box StatsD supports: • Graphite (of course) • Console for debugging/troubleshooting • Repeater for relaying StatsD packets Friday, November 2, 12

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

Don’t see what you like? • creating a custom backend is easy. • the repeater makes it easy to experiment. Friday, November 2, 12

Slide 9

Slide 9 text

Just got easier • Previously Backends calculated data. • Pull request in to move calculations out of backends. • Simplifies backends even more. Friday, November 2, 12

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

Thanks! • Dan Rowe • @draco2002 • drowe@wayfair.com • https://github.com/draco2003 Friday, November 2, 12