[Hawkular-dev] Integrate metric data with inventory

[Thomas Segismont]

Great!

Le 16/07/2016 à 01:59, John Mazzitelli a écrit :
> HawkFX does look at it, yes. (that PR got merged a few days ago).
>
> The ruby client needs to add it - Heiko asked that I create an issue for it, which I did. It is here:
>
> https://github.com/hawkular/hawkular-client-ruby/issues/110
>
> ----- Original Message -----
>> That sounds like a nice solution to me. That would allow to keep the
>> existing metric names. My only concern is the following: is this
>> metric-id attribute something clients like HawkFx and ManageIQ provider
>> look at?
>>
>> Le 15/07/2016 à 14:01, John Mazzitelli a écrit :
>>>> So h-inventory metric has a property 'metric-id', this property is used
>>>> for
>>>> mapping h-metric metric, right?
>>>
>>> Yes.
>>>
>>> "metric-id" is an optional property - it does not have to exist. But if it
>>> does exist, yes, that is your explicit mapping to the hawkular-metric ID.
>>>
>>> If "metric-id" property does NOT exist on the inventory metric, then you
>>> assume the inventory ID is the same as the hawkular-metrics ID.
>>>
>>> ----- Original Message -----
>>>> Ok!
>>>> So h-inventory metric has a property 'metric-id', this property is used
>>>> for
>>>> mapping h-metric metric, right?
>>>> Thanks
>>>>
>>>> On Thu, Jul 14, 2016 at 5:40 PM Lukas Krejci < lkrejci at redhat.com > wrote:
>>>>
>>>>
>>>> On čtvrtek 14. července 2016 9:16:36 CEST Austin Kuo wrote:
>>>>> Hi,
>>>>> I’m currently working on vertx metric agent, my job is to enable the
>>>>> inventory such that users can view the inventory and corresponding
>>>>> metrics.
>>>>> My question is that how “real metric data” and “inventory metrics” are
>>>>> matched?
>>>>> Is it simply bound via id?
>>>>>
>>>>
>>>> There is no predefined way of doing it actually. It might be by id (or you
>>>> can
>>>> use inventory's canonical path of the metrics as its id in h-metrics) or
>>>> even
>>>> use a different ID in h-metrics and only store an info about it in
>>>> inventory.
>>>> This is actually what wildfly agent is currently doing (see the thread
>>>> starting with
>>>> http://lists.jboss.org/pipermail/hawkular-dev/2016-July/002973.html ).
>>>>
>>>>> Thanks,
>>>>> Austin
>>>>
>>>>
>>>> --
>>>> Lukas Krejci
>>>>
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>
>> --
>> Thomas Segismont
>> JBoss ON Engineering Team
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>

-- 
Thomas Segismont
JBoss ON Engineering Team