Find your agents with Jolokia 1.2.0

New year, new release. Jolokia 1.2.0 is in the house.

Ok, it’s not the BIG 2.0 which was already somewhat promised. Anyways, another big feature jumped on the 1.x train in the last minute. It is now possible to find agents in your network by sending an UDP packet via multicast. Agents having this discovery mechanism enabled will respond with their meta data including the access URL. This is especially useful for clients who want to provide access to agents without much configuration. I.e. the excellent HTML5 console will probably use it one way or the other. In fact, it was which put me on track for this nice little feature ;-)

Discovery is enabled by default for the JVM agent, but not for the WAR agent. It can be easily enabled for the WAR agent by using servlet init parameters, system properties or environment variables. All the nifty details can be found in the reference manual.

The protocol for the discovery mechanism is also defined in the reference manual. One of the first clients supporting this discovery mode is Jmx4Perl in its newest version. The Jolokia Java client will follow in one of the next minor releases.

For sending a multicast request discovery message, an UDP message should be send to the address, port 24884 which contains a JSON message encoded in UTF-8 with the following format

    "type": "query"

Any agent enabled for discovery will respond to the requestor on the same socket with an answer which looks like

    "type": "response",
    "agent_description" : "Atlantis Tomcat",
    "agent_id" : "",
    "url": "",
    "server_vendor" : "Apache",
    "server_product" : "Tomcat",
    "server_version" : "7.0.35"

The response itself is a JSON object, too. Responses are sent back to the address and port of the sender of the query request.

But you don’t need client support for multicast requests if you know already the URL for one agent. Each agent registers a MBean jolokia:type=Discovery which perform the multicast discovery request for you if you trigger the operation lookupAgents. The returned value is similar as shown in the example above.

Happy multicasting, and don’t forget to open an issue in case of troubles.

Monitoring-Workshop 2017 12./13.9. Düsseldorf