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