Architecture overview of Nagios and Talend ESB
This is a diagram of how the Nagios functionality is integrated into Talend ESB- typically, the Nagios server is monitoring the OSGi container on the right, which may be a Talend Runtime Container:
Jmx4Perl provides an alternative way of accessing JMX (Java Management Extensions) on JEE Servers or OSGi containers. It uses an agent-based approach where a small Java Web application (Jolokia), is deployed on the application server, and provides HTTP/JSON-based access to JMX MBeans registered within the application server.
In Talend ESB, for convenience, Jolokia has been integrated into the Talend Runtime Container as an OSGi agent and also integrated into ActiveMQ using a JAR file.
This table is an overview of components in the jmx4perl distribution:
| Component | Description |
|---|---|
| jmx4perl plugin | This installed on the same machine as Nagios; it communicates with a Jolokia agent which is integrated with the Talend ESB containers. |
| Jolokia |
Jolokia is an HTTP/JSON bridge for efficent remote JMX access. It is a separate agent that resides on the monitored server, and works with the jmx4perl plugin. Jolokia is based on a set of Perl modules, and does not need a local Java installation. It is pre-installed into Talend ESB containers and ActiveMQ. |
| check_jmx4perl | A command utility on the Nagios server that can be used to get the monitored data - it is part of the jmx4perl distribution. |
| JMX::Jmx4Perl | a Perl library, for programmatic JMX access. |
For more information, see:
- Nagios: http://www.nagios.com
- Jolokia: http://www.jolokia.org
- Jmx4perl: http://labs.consol.de/jmx4perl
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!