[Hawkular-dev] availability and metric endpoints

Thomas Segismont tsegismo at redhat.com
Mon Mar 23 09:34:47 EDT 2015


Le 23/03/2015 12:28, Heiko W.Rupp a écrit :
> On 23 Mar 2015, at 11:04, Thomas Segismont wrote:
>
>> Le 23/03/2015 09:04, Heiko W.Rupp a écrit :
>>> But first: do we know that we need counters and gauges right now?
>>
>> I can't see why need special semantics for storing values coming from
>> counters and gauges (and availability).
>
> If they need no special semantics, why would one want to add counters
> and gauges?
>
>
> And for availability, do we really want to have feeds deliver random
> numbers
> as their availability and then in the UI show the random numbers as we
> can
> not determine what availability state they mean?
>
> If all you have is a double, then everything will look like
> 2.999999975687 pentium processors :)

What I meant is that we shouldn't care about how the data is stored, if 
it's a counter, a gauge, a string. It's a "value point" in time.

What matters is how we query this data. For example, if you're working 
with a counter you'll probably be interested in applying a derivative 
function.


More information about the hawkular-dev mailing list