Monitoring other systems using the Camel JMX Component

Camel includes a JMX Component that can be a JMX consumer for other systems. That is, it can connect to a local or remote JMX MBean server and listen for JMX Notifications that will then flow through the specified Camel route. This component also includes the ability to create and register local JMX Monitor beans that will create JMX Notifications based on changes in other JMX MBeans.

This combination of capabilities—consuming JMX Notifications, and creating local Monitor beans that can generate JMX Notifications—gives you some extra options in terms of monitoring your integration routes. For example, if you have systems deployed remotely across a WAN, you can use this mechanism to aggregate and report on JMX metrics in that remote system onto a channel such as a JMS queue. You can then use this to gather up information within your Data Center.

This recipe will show you how to use the Camel JMX Component to create and register a monitor...