12:08 a.m.
Hi, all.
This is Austin.
I've been trying to understand how the inventory in agent works.
As far as I understand, an inventory is a graph, and the agent sends the
graph to the hawkular server with some kind of format. Such that the
hawkular server can answer queries with the data that the agent sends.
I have a few of questions:
1. What are the various protocols for(dmr, jmx, platform)?
2. And there's Resource and ResourceType, each of them holds a graph,
what's the relation between them? Are they isomorphic and each node of
ResouceType annotates the corresponding Resource node?
Thanks!
7:43 a.m.
Hey,
1. What are the various protocols for(dmr, jmx, platform)?
That is mostly on how to obtain the data. Dmr is some
Wildlfy-internal protocol, that is detyped and can be
accessed from external with some sort of rest-api.
Jmx are the java management extensions and can be
used to talk to remote java vms and obtain management
information from there.
2. And there's Resource and ResourceType, each of them holds a
graph,
what's the relation between them? Are they isomorphic and each node of
ResouceType annotates the corresponding Resource node?
No. It is rather the relation of class (=ResourceType) and
its instantiated object (=Resource). Check e.g. the Datasources
where you have one ResourceType "DataSource" and multiple
datasources of this type like HawkularDS and KeycloakDS
5:01 a.m.
Hi Austin,
On 2016-03-13 13:43, Heiko W.Rupp wrote:
Hey,
> 1. What are the various protocols for(dmr, jmx, platform)?
That is mostly on how to obtain the data. Dmr is some
Wildlfy-internal protocol, that is detyped and can be
accessed from external with some sort of rest-api.
Jmx are the java management extensions and can be
used to talk to remote java vms and obtain management
information from there.
Yes, the various protocols are ways how the Agent is able to both
discover resources and also collect metrics about them.
-- Peter
> 2. And there's Resource and ResourceType, each of them
holds a graph,
> what's the relation between them? Are they isomorphic and each node of
> ResouceType annotates the corresponding Resource node?
No. It is rather the relation of class (=ResourceType) and
its instantiated object (=Resource). Check e.g. the Datasources
where you have one ResourceType "DataSource" and multiple
datasources of this type like HawkularDS and KeycloakDS
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:35 a.m.
Many thanks to Heiko for giving such a clear example of classes and objects
and Peter for elaboration. :)
On Mon, Mar 14, 2016 at 6:01 PM Peter Palaga <ppalaga(a)redhat.com> wrote:
Hi Austin,
On 2016-03-13 13:43, Heiko W.Rupp wrote:
> Hey,
>
>> 1. What are the various protocols for(dmr, jmx, platform)?
>
> That is mostly on how to obtain the data. Dmr is some
> Wildlfy-internal protocol, that is detyped and can be
> accessed from external with some sort of rest-api.
> Jmx are the java management extensions and can be
> used to talk to remote java vms and obtain management
> information from there.
Yes, the various protocols are ways how the Agent is able to both
discover resources and also collect metrics about them.
-- Peter
>> 2. And there's Resource and ResourceType, each of them holds a
graph,
>> what's the relation between them? Are they isomorphic and each node
of
>> ResouceType annotates the corresponding Resource node?
>
> No. It is rather the relation of class (=ResourceType) and
> its instantiated object (=Resource). Check e.g. the Datasources
> where you have one ResourceType "DataSource" and multiple
> datasources of this type like HawkularDS and KeycloakDS
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:42 a.m.
In case you haven't found it already, hawkular.org contains a little bit
of documentation on various types of entities inventory understands and
how they are organized:
http://www.hawkular.org/docs/components/inventory/index.html
On 03/14/2016 11:35 AM, Austin Kuo wrote:
Many thanks to Heiko for giving such a clear example of classes and
objects
and Peter for elaboration. :)
On Mon, Mar 14, 2016 at 6:01 PM Peter Palaga <ppalaga(a)redhat.com> wrote:
> Hi Austin,
>
> On 2016-03-13 13:43, Heiko W.Rupp wrote:
>> Hey,
>>
>>> 1. What are the various protocols for(dmr, jmx, platform)?
>>
>> That is mostly on how to obtain the data. Dmr is some
>> Wildlfy-internal protocol, that is detyped and can be
>> accessed from external with some sort of rest-api.
>> Jmx are the java management extensions and can be
>> used to talk to remote java vms and obtain management
>> information from there.
>
> Yes, the various protocols are ways how the Agent is able to both
> discover resources and also collect metrics about them.
>
> -- Peter
>
>>> 2. And there's Resource and ResourceType, each of them holds a
> graph,
>>> what's the relation between them? Are they isomorphic and each node
> of
>>> ResouceType annotates the corresponding Resource node?
>>
>> No. It is rather the relation of class (=ResourceType) and
>> its instantiated object (=Resource). Check e.g. the Datasources
>> where you have one ResourceType "DataSource" and multiple
>> datasources of this type like HawkularDS and KeycloakDS
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
--
Lukas Krejci
2975
days inactive
2976
days old
4 comments
4 participants
participants (4)
-
Austin Kuo -
Heiko W.Rupp -
Lukas Krejci -
Peter Palaga