Added statsd binding for Go into examples
.mean was replaced with .mean_<threshold>, so update unit tests.
…hold Changed config.percentThreshold to also accept a list of percentiles.
This prevents '99.99' from being split into two directories by changing it to '99_99'.
The percentThreshold config parameter can now accept a single value or a list of values. A statistic for each percentile threshold will be generated analogous to how the single-value threshold stats were generated before. Updated documentation and example config file as well.
Based on feedback from Erik Kastner, this change makes it so all gauge values will get stored in carbon using a "stats.gauges." prefix, similar to the way timers work today.
Some applications have absolute values that they'd like to track as a simple gauge, rather than as a count per period. This change adds support for this type. Clients can set a gauge by sending 'value|g'. Any gauge value which is set will persist and be flushed out to graphite each iteration. This means that the gauge can be set once, and that value will be graphed continuously until the next time it's set.
Update Java client with java.nio package
Fixed Rails Example
Thanks for librato for the package.json (with edits). This is the start of getting StatsD more integrated with the Node / NPM Ecosystem. "npm test" now runs the tests, and we have a version number and stuff.
…ull request #6
…red by python_example.py.
…ejs from /usr/bin/nodejs to /usr/bin/node between maverick and natty
…, it's dangerous and not persitent in many cases (/tmp mount in tmpfs or wiped at host startup).
…an/ubuntu distro. while fabric user... less likely.
…u Maverick, which come with nodejs 0.1.97. but execution fail
C# client example