A first implementation can be found on gerrit[3].
# How to monitor the engine?
It is as easy as starting a hystrix-dashboard [2] with
$ git clone https://github.com/Netflix/Hystrix.git
$ cd Hystrix/hystrix-dashboard
$ ../gradlew jettyRun
# Security?
In the provided patches the hystrix-metrics-servlet is accessible at
/ovirt-engine/api/hystrix.stream. It is protected by basic auth but accessible
for everyone who can authenticate. We should probably restrict it to admins.that would be great if it doesn't require too much work. If it does then we can start with enabling/disabling via JMX using Roy's recent patch [8]
3) Three unpackaged dependencies: archaius, hystrix-core, hystrix-contrib
Since you yesterday volunteered to package them I think this should not stop us!:-)thanks a lot for the effort, I miss a proper analysis for soooo long. Thanks for stepping up!michal[8] https://gerrit.ovirt.org/#/c/29693/
# References
[1] https://github.com/Netflix/Hystrix
[2] https://github.com/Netflix/Hystrix/tree/master/hystrix-dashboard
[3] https://gerrit.ovirt.org/#/q/topic:hystrix
[4] http://www.nurkiewicz.com/2015/02/storing-months-of-historical-metrics.html
[5] https://github.com/Netflix/Hystrix/wiki/FAQ#what-is-the-processing-overhead-of-using-hystrix
[5] https://bugzilla.redhat.com/show_bug.cgi?id=1268216
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1268224
[7] http://graphite.wikidot.com
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel