manual:config:items:itemtypes:jmx_monitoring

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:config:items:itemtypes:jmx_monitoring [2021/02/26 08:24]
martins-v formatting fix
manual:config:items:itemtypes:jmx_monitoring [2021/03/16 12:18]
martins-v using custom endpoint with JBoss EAP 6.4
Line 159: Line 159:
 Since Zabbix 4.0.0 it is possible to work with custom MBeans returning non-primitive data types, which override the **toString()** method. Since Zabbix 4.0.0 it is possible to work with custom MBeans returning non-primitive data types, which override the **toString()** method.
  
-=== Custom ​endpoint ​example ​with JBoss EAP 6.4 ===+=== Using custom ​endpoint with JBoss EAP 6.4 ===
  
 Custom endpoints allow working with different transport protocols other than the default RMI. Custom endpoints allow working with different transport protocols other than the default RMI.
Line 189: Line 189:
 {{:​manual:​config:​items:​itemtypes:​jmx_jboss_example.png?​600|}} {{:​manual:​config:​items:​itemtypes:​jmx_jboss_example.png?​600|}}
  
-As we know that this version of JBoss uses the the JBoss Remoting protocol instead of RMI, we may mass update the JMX endpoint parameter in our JMX template accordingly:​+As we know that this version of JBoss uses the the JBoss Remoting protocol instead of RMI, we may mass update the JMX endpoint parameter ​for items in our JMX template accordingly:​
  
   service:​jmx:​remoting-jmx://​{HOST.CONN}:​{HOST.PORT}   service:​jmx:​remoting-jmx://​{HOST.CONN}:​{HOST.PORT}
  
-{{:​manual:​config:​items:​itemtypes:​jmx_jboss_example3.png?600|}}+{{:​manual:​config:​items:​itemtypes:​jmx_jboss_example_b.png|}}
  
 Let's update the configuration cache: Let's update the configuration cache: