Hide Forgot
The following page talks about https://www.ovirt.org/develop/developer-guide/engine/jmx-support/. But it's too short. WildFly use a custom jmx transport, so jconsole can't be used out of the box. The usual -Dcom.sun.management.jmxremote don't work too. To use jconsole, it's needed to use some custom jar from WildFly or use the provided jconsole.sh. It's should be explained in the documentation.
Documentation is for users, not developers (apart from the REST API, SDKs, etc.) Why is the JMX need to be documented? What exactly is missing?
Because we use a lot JMX for monitoring of your products and tools, it's quite common in java world. So it was easy to add oVirt to that instead of using a custom setup. We use this: http://jrds.fr/sourcetype/jmx/start.
(In reply to Fabrice Bacchella from comment #2) > Because we use a lot JMX for monitoring of your products and tools, it's > quite common in java world. So it was easy to add oVirt to that instead of > using a custom setup. > > We use this: http://jrds.fr/sourcetype/jmx/start. OK, so the approach we are pursuing is monitoring the JMX via Collectd plugin. See https://bugzilla.redhat.com/show_bug.cgi?id=1435994 - and please comment on it.
Done: https://bugzilla.redhat.com/show_bug.cgi?id=1435994#c3. Do you need more details on it ?