There is a bit of a pitfail with gauges in statsd: if you send a number with a sign (any sign), statsd will add/subtract the value instead of setting it. Say, if you send a metric with "-1" over time, graphite (or whatever is that that your statsd is configured to work with) will draw a downward trend, which isn't expected/intuitive behaviour at all. The user is going to have to go and find this special case in the statsd docs. I propose that a new method will be added to statsd.Gauge to set the metric value no matter the sign. What do you think?
Hi and thanks for this project
There is a bit of a pitfail with gauges in statsd: if you send a number with a sign (any sign), statsd will add/subtract the value instead of setting it. Say, if you send a metric with "-1" over time, graphite (or whatever is that that your statsd is configured to work with) will draw a downward trend, which isn't expected/intuitive behaviour at all. The user is going to have to go and find this special case in the statsd docs. I propose that a new method will be added to statsd.Gauge to set the metric value no matter the sign. What do you think?