I think adding *some* websocket support would be nice. Some meaning
limited feature set for relevant use cases (like the one pointed out by
Mike). Not the whole REST API duplication you're referring to.
Plus a limited feature set can be implemented in a reasonable amount of
time. That is quite important given that pre-computed
aggregates/downsampling should get most of our bandwith IMO.
Le 17/03/2016 10:38, Michael Burman a écrit :
Hi,
+1 on this feature, we really should revisit the websocket API and make it work (for
agent communication, for UI, etc).
- Micke
----- Original Message -----
From: "mike thompson" <mithomps(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Wednesday, March 16, 2016 7:57:49 PM
Subject: Re: [Hawkular-dev] Hawkular Metrics - Roadmap
I didn’t see any mention of streaming metrics. I know this is something that we had
discussed. Since we already have observables in Metrics, opening up a web socket and
streaming the metrics updates seems like a natural fit and capability that few solutions
currently have to offer.
Also, providing an Rx.js consumer on the hawkular charts side would allows to chart in
real-time metrics with minimal bandwidth (especially with dashboards and NOCs)
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev