Bug 1332467

Summary: [RFE] jmx is not explained in the documentation
Product: [oVirt] ovirt-engine Reporter: Fabrice Bacchella <fabrice.bacchella>
Component: DocumentationAssignee: Martin Perina <mperina>
Status: CLOSED DEFERRED QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.5.1CC: adahms, bugs, fabrice.bacchella, rgolan
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-25 14:47:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Fabrice Bacchella 2016-05-03 09:27:55 UTC 
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.
Comment 1 Yaniv Kaul 2017-06-07 18:54:58 UTC 
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?
Comment 2 Fabrice Bacchella 2017-06-07 20:45:46 UTC 
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.
Comment 3 Yaniv Kaul 2017-06-07 20:48:39 UTC 
(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.
Comment 4 Fabrice Bacchella 2017-06-07 20:59:16 UTC 
Done: https://bugzilla.redhat.com/show_bug.cgi?id=1435994#c3.

Do you need more details on it ?