Unable to use non-integer metrics for gauge and meter. about go-metrics HOT 6 CLOSED

Gauge in the JVM metrics is a generic, which would be great, and I guess we could make this one an interface{}, but I think the common case is an integer and that's served most users pretty well. (Case in point: you're the first to point this out.)

metrics.Meter is meant to capture the rate of events which are discrete events. Its Mark method records one or more events but the idea of recording 3.14159 events doesn't really make sense to me, even if the math works.

from go-metrics.

@usmanismail what if we added a new metric type that operates like Gauge but on an interface{}? Reporters would just format such metrics with "%v". Proposals for the name are welcome, too.

from go-metrics.

Its true that could work but we would be trusting the downstream code to return a valid interface otherwise Reporters will have to handle the garbled text.

As far as I can see the only missing usecase is floating point numbers. So maybe we can just add a FloatingPointGauge.

from go-metrics.

I've implemented a float64 version of Gauge. Please comment on #44 on the proposal.

from go-metrics.

There are many gauges which are not integers: temperature, stock/currency prices, loadavg, database settings, and just about any analog reading.

from go-metrics.

Closed per #44.

from go-metrics.