So counters  and sets exist (and work) in the linked (proposed) deb.  Out of the box timers I think are lower/count (of all the timers matching that key)/mean/upper/upper_99.

Chase

On 6/3/14, 1:34 PM, Matthew Walker wrote:

Plugging for additional functionality -- it would also be ridiculously cool is if we had the ability to count uniques (sets in the etsy statsd implementation).

~Matt Walker

Wikimedia Foundation

Fundraising Technology Team

On Tue, Jun 3, 2014 at 11:22 AM, Matthew Walker <mwalker@wikimedia.org> wrote:

Can you help me understand what the weird behavior you are seeing with counters is?  I'm pretty familiar with statsd types overall so I can tell you if this would solve the issue.

Simply, metrics like "ocg.pdftest_counter:1|c" do not count, instead it keeps the last sent value and persists that. It's behaving like a gauge. The work around is to use the meter metric type. Which provides the 'counts / period' stats I'm actually looking for as well as the absolute count.

This version also comes with some timer niceties which would easy to amend / append to.  It would be good to lock down the use case here to make sure things will work as you hope.

I'm happy with the current timer implementation gives us (though arguably it's actually acting as the histogram type). Essentially, I'm going to be looking for the mean time, the stddev, and some sort of top range 95%/99% information.