Batsd: 37 Signals' Ruby Statsd implementation persisting to Redis

Re:Batsd: 37 Signals' Ruby Statsd implementation persisting ... by uggedal on Wednesday May 30, 2012 @03:39PM (#4044462)

Those interested in lower memory consumption and efficiency should take a look at https://github.com/armon/statsite another statsd "clone". Originally a Python implementation statsite is now rewritten in C.

[ Parent | on HN ]

Re:Batsd: 37 Signals' Ruby Statsd implementation persisting ... by taligent on Wednesday May 30, 2012 @04:42PM (#4044728)

I wouldn't exactly call that a clone since it doesn't support key features of statsd (e.g. gauges) and has unique features of its own (e.g. key/value pairs).

Looks brilliant otherwise.

[ Parent | on HN ]

Re:Batsd: 37 Signals' Ruby Statsd implementation persisting ... by armon on Friday June 01, 2012 @04:36PM (#4055615)

It is actually just a difference of naming. Gauges in statsd operate the same as kv data in statsite. Originally, both projects referred to them as kv, this seems to be a more recent change in statsd.

[ Parent | on HN ]

Re:Batsd: 37 Signals' Ruby Statsd implementation persisting ... by DavidAbrams on Wednesday May 30, 2012 @05:39PM (#4045053)

+1 for saying "key/value" instead of "key-value".

[ Parent | on HN ]