Statsd is a simple client/server mechanism from the folks at Etsy that allows operations and development teams to easily feed a variety of metrics into a Graphite system. For more info on statsd read the seminal blog article on Statsd “Measure Anything, Measure Everything”.
As would be expected there are statsd clients in many languages. But, there are also many implementations of the statsd server. This is nice because each organization can pick the one that best fits them. For example, a python shop might prefer to deploy a python based statsd instead of Etsy’s original node.js implementation. Also, there are some statsd implementations that diverge from the original design and provide additional features.
I could not find a single resource that listed all of the different implementations, so I figured I would try to start one here.
- Etsy’s statsd: node.js. The Original
- petef-statsd: ruby. Supports AMQP.
- statsd_rb: ruby.
- quasor/statsd: ruby. can send data to graphite or mongoDB
- py-statsd: python (including python client code).
- zbx-statsd: python, based on py-statsd. Sends data to Zabbix instead of graphite.
- statsd.scala: scala. Sends data to Ganglia instead of Graphite. Different messaging protocol, uses JSON.
- txStatsD: python + twisted, from the folks @ Canonical
- statsd-librato: node.js. Fork of etsy’s statsd for sending data to Librato instead of graphite from the folks @ Engine Yard.
- estatsd: erlang. From the folks @ Opscode
- statsite: python
- metricsd: scala. Should be drop-in compatible with etsy’s statsd, but with support for additional metric types (eg: meter, gauge, histogram)
- statsd-c: C. compatible with original etsy statsd
- statsd (librato): node.js. Librato’s officially maintained fork of statsd based on the changes from Engine Yard. Supports multiple graphing services including Librato Metrics
- bucky: python. A unique spin on statsd that supports collecting data from statsd clients, collectd, and metricsd, with output to graphite. The ability to translate collectd plugin names to be more graphite-friendly is very compelling.
Please leave a comment if you have an implementation that should be listed here. Feedback on any of the above implementations would be helpful too.
Source: http://joemiller.me/2011/09/21/list-of-statsd-server-implementations/ additional implementations listed in the comments.