Details

    • Type: Problem report
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 3.0.3
    • Fix Version/s: None
    • Component/s: Java gateway (J)
    • Labels:

      Description

      The current Zabbix JMX out-of-the-box monitoring capabilities are somewhat limited. The two most significant limitations are

      a) you can only monitor standard JMX URLs
      b) you can't access TabularData structures in the JMX target

      The attached patch addresses both of these limitations. It is complete upgrade safe and backwards compatible so existing JMX monitoring won't be affected at all.

      It adds some functionality to the DNS field for a hosts JMX Agent configuration. Instead of a regular DNS hostname you can enter a regular JMX service URL with e.g. different transports like this: service:jmx:remote+http://wildfly1-2-vl:8330
      All you need to do is to add the transport jar to the classpath of the JavaGateway.

      I also added a second patch that increases the max DNS hostname field length from 64 to 255 characters to allow for more complex JMX service URLs like this: service:jmx:rmi://esb1-3-vl.dfwx:44448/jndi/rmi://esb1-3-vl.dfwx:1103/karaf-camel-call-handler-1

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                SunFire Thorsten Kunz
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: