8:51 a.m.
Hi,
The current status is that I have created
- a feed
- a root resource with a resource type
- a eventbus resource as a child of the root resource above with a
resource type
- a eventbus.handlers metrics with gauge metric type. This has a
property 'metric-id' corresponding to the id of the metric data.
Fortunately, now I can view the metric data graph from the client (hawkfx).
Austin,
Thanks.
10:39 p.m.
Great.
I believe you should start working on HttpServer reporting now (type +
resource + 1 metric).
IMO, you would benefit from extracting the Inventory HTTP client code
into something reusable to report different resources and types.
Regards,
Thomas
Le 19/07/2016 à 08:51, Austin Kuo a écrit :
Hi,
The current status is that I have created
* a feed
* a root resource with a resource type
* a eventbus resource as a child of the root resource above with a
resource type
* a eventbus.handlers metrics with gauge metric type. This has a
property 'metric-id' corresponding to the id of the metric data.
Fortunately, now I can view the metric data graph from the client
(hawkfx).
Austin,
Thanks.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
10:03 a.m.
no problem but why just 1 metric since there are a lot?
On Thu, Jul 21, 2016 at 4:39 AM Thomas Segismont <tsegismo(a)redhat.com>
wrote:
Great.
I believe you should start working on HttpServer reporting now (type +
resource + 1 metric).
IMO, you would benefit from extracting the Inventory HTTP client code
into something reusable to report different resources and types.
Regards,
Thomas
Le 19/07/2016 à 08:51, Austin Kuo a écrit :
> Hi,
> The current status is that I have created
>
> * a feed
> * a root resource with a resource type
> * a eventbus resource as a child of the root resource above with a
> resource type
> * a eventbus.handlers metrics with gauge metric type. This has a
> property 'metric-id' corresponding to the id of the metric data.
> Fortunately, now I can view the metric data graph from the client
> (hawkfx).
>
> Austin,
> Thanks.
>
>
>
> _______________________________________________
> 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
10:24 p.m.
1 metric was just for the "start" :)
Of course more is better
Le 21/07/2016 à 10:03, Austin Kuo a écrit :
no problem but why just 1 metric since there are a lot?
On Thu, Jul 21, 2016 at 4:39 AM Thomas Segismont <tsegismo(a)redhat.com
<mailto:tsegismo@redhat.com>> wrote:
Great.
I believe you should start working on HttpServer reporting now (type +
resource + 1 metric).
IMO, you would benefit from extracting the Inventory HTTP client code
into something reusable to report different resources and types.
Regards,
Thomas
Le 19/07/2016 à 08:51, Austin Kuo a écrit :
> Hi,
> The current status is that I have created
>
> * a feed
> * a root resource with a resource type
> * a eventbus resource as a child of the root resource above with a
> resource type
> * a eventbus.handlers metrics with gauge metric type. This has a
> property 'metric-id' corresponding to the id of the metric data.
> Fortunately, now I can view the metric data graph from the client
> (hawkfx).
>
> Austin,
> Thanks.
>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@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
10:16 a.m.
Hi,
I've already add the http resource and the metric, but there seems to be a
bug that inventory does not allow concurrent transactions when creating
multiple resource types at the same time. If I send the request one by one,
it's working, but it should be executed concurrently. So I'm waiting for
the fix before submitting the PR.
Austin.
On Tue, Jul 26, 2016 at 4:24 AM Thomas Segismont <tsegismo(a)redhat.com>
wrote:
1 metric was just for the "start" :)
Of course more is better
Le 21/07/2016 à 10:03, Austin Kuo a écrit :
> no problem but why just 1 metric since there are a lot?
>
>
> On Thu, Jul 21, 2016 at 4:39 AM Thomas Segismont <tsegismo(a)redhat.com
> <mailto:tsegismo@redhat.com>> wrote:
>
> Great.
>
> I believe you should start working on HttpServer reporting now (type
+
> resource + 1 metric).
>
> IMO, you would benefit from extracting the Inventory HTTP client code
> into something reusable to report different resources and types.
>
> Regards,
> Thomas
>
> Le 19/07/2016 à 08:51, Austin Kuo a écrit :
> > Hi,
> > The current status is that I have created
> >
> > * a feed
> > * a root resource with a resource type
> > * a eventbus resource as a child of the root resource above with
a
> > resource type
> > * a eventbus.handlers metrics with gauge metric type. This has a
> > property 'metric-id' corresponding to the id of the metric
data.
> > Fortunately, now I can view the metric data graph from the
client
> > (hawkfx).
> >
> > Austin,
> > Thanks.
> >
> >
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@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
2:07 p.m.
Also, I jus thought of a few of questions:
1. Does a kind of resource have an unique resource type ?
2. Does a kind of metric have an unique metric type? or for
example, all counter metrics can share the same type (counter)...
Thanks.
On Tue, Jul 26, 2016 at 4:16 PM Austin Kuo <auszon3(a)gmail.com> wrote:
Hi,
I've already add the http resource and the metric, but there seems to be a
bug that inventory does not allow concurrent transactions when creating
multiple resource types at the same time. If I send the request one by one,
it's working, but it should be executed concurrently. So I'm waiting for
the fix before submitting the PR.
Austin.
On Tue, Jul 26, 2016 at 4:24 AM Thomas Segismont <tsegismo(a)redhat.com>
wrote:
> 1 metric was just for the "start" :)
>
> Of course more is better
>
> Le 21/07/2016 à 10:03, Austin Kuo a écrit :
> > no problem but why just 1 metric since there are a lot?
> >
> >
> > On Thu, Jul 21, 2016 at 4:39 AM Thomas Segismont <tsegismo(a)redhat.com
> > <mailto:tsegismo@redhat.com>> wrote:
> >
> > Great.
> >
> > I believe you should start working on HttpServer reporting now
> (type +
> > resource + 1 metric).
> >
> > IMO, you would benefit from extracting the Inventory HTTP client
> code
> > into something reusable to report different resources and types.
> >
> > Regards,
> > Thomas
> >
> > Le 19/07/2016 à 08:51, Austin Kuo a écrit :
> > > Hi,
> > > The current status is that I have created
> > >
> > > * a feed
> > > * a root resource with a resource type
> > > * a eventbus resource as a child of the root resource above
> with a
> > > resource type
> > > * a eventbus.handlers metrics with gauge metric type. This has a
> > > property 'metric-id' corresponding to the id of the metric
> data.
> > > Fortunately, now I can view the metric data graph from the
> client
> > > (hawkfx).
> > >
> > > Austin,
> > > Thanks.
> > >
> > >
> > >
> > > _______________________________________________
> > > hawkular-dev mailing list
> > > hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org
> >
> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@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
>
2839
days inactive
2846
days old
5 comments
2 participants
participants (2)
-
Austin Kuo -
Thomas Segismont