<div dir="ltr">no problem but why just 1 metric since there are a lot?<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 21, 2016 at 4:39 AM Thomas Segismont <<a href="mailto:tsegismo@redhat.com">tsegismo@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Great.<br>
<br>
I believe you should start working on HttpServer reporting now (type +<br>
resource + 1 metric).<br>
<br>
IMO, you would benefit from extracting the Inventory HTTP client code<br>
into something reusable to report different resources and types.<br>
<br>
Regards,<br>
Thomas<br>
<br>
Le 19/07/2016 à 08:51, Austin Kuo a écrit :<br>
> Hi,<br>
> The current status is that I have created<br>
><br>
> * a feed<br>
> * a root resource with a resource type<br>
> * a eventbus resource as a child of the root resource above with a<br>
> resource type<br>
> * a eventbus.handlers metrics with gauge metric type. This has a<br>
> property 'metric-id' corresponding to the id of the metric data.<br>
> Fortunately, now I can view the metric data graph from the client<br>
> (hawkfx).<br>
><br>
> Austin,<br>
> Thanks.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
><br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org" target="_blank">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
</blockquote></div>