How can I request it receive higher priority? :)
If we are going to start allowing external feeds and agents to send in metric/avail data,
we are going to need to have at least a minimal UI to just see the data (even if its a
little HTML <table> with the data in it). Anything to at least verify the data is
getting in there and is what we expect it to be.
Right now, AFAIK, we are limited to seeing metrics and avail for URL pings... that is
going to get boring after a while :) If we had a generic metrics UI, we'd be able to
see data for any subsystem in Wildfly.
----- Original Message -----
> On 14 Apr 2015, at 07:59, John Mazzitelli <mazz(a)redhat.com> wrote:
>
> Can someone describe to me what needs to be done to see the
> Hawkular-Metrics UI (the explorer)? If I store metric and avail data into
> kettle via the Metrics REST API, I can't use the kettle UI because it is
> geared to the pinger.
>
> Is there a explorer UI that comes with kettle outside of the main hawkular
> UI? If not, is there something I have to do to enable that explorer
> webapp?
A month or so ago I would have said "The explorer gets deployed with
hawkular-metrics so just
http://localhost:8080/explorer
<
http://localhost:8080/explorer>”.
However, there is no start.sh now, and deployment is deferred to Hawkular
kettle. So there is a javascript app with no war for deployment. Also the
REST urls have changed and will change again soon.
In short, it looks the explorer needs a considerable amount of attention to
make it work with latest hawkular kettle. This effort will need to be
prioritised with the normal hawkular UI work.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev