Managing Remote JMX Metrics in ODH Components

Most of ODH components expose metrics over JMX. To access these metrics outside of this process, use the remoteJMX metrics utility helper function to manage remote JMX metrics on demand through a custom bootstrap script.

Enabling remoteJMX requires updating JVM arguments for java process of each ODH component. Each Ambari service has service-env shell script template which deals with JVM arguments. This shell script template can be modified to enable and manage remoteJMX. To simplify management of remoteJMX there's a config property in Ambari for each component to enable/disable remoteJMX. For each component, go to the Configs section for each service in the Ambari UI, and then look for properties with following syntax:

• odh.<service-name>.<component-name>.jmxremote

  This property is exposed as a toggle in the Ambari UI and is used for enabling and disabling remoteJMX for respective service and component.

• odh.<service-name>.<component-name>.jmxremote.port

  This property denotes the remoteJMX port that the component JVM process exposes metrics.

The config toggle in Ambari UI enables remoteJMX for the component with default values as described below. To add JVM properties for remoteJMX, edit the <service>-env.sh config template in the Ambari UI.

• -Dcom.sun.management.jmxremote=true
• -Dcom.sun.management.jmxremote.ssl=false
• -Dcom.sun.management.jmxremote.port=<port_value_for_component>
• -Dcom.sun.management.jmxremote.authenticate=false

The following is the complete list of all Ambari config properties to manage remote JMX: