IntroductionThe probes available in the Petals internals and components are able to send JMX notifications when they detect a defect. These notifications can be sent to Nagios with a dedicated monitoring command of Petals CLI that receive JMX notifications and write them in the channel of Nagios passive checks.
The daemon petals-cli-nagios listen JMX notifications coming from Petals ESB nodes using a dedicated Petals CLI command. When it receives a JMX notification, it formats and prints an external command for Nagios. The host and service emitting the JMX notification are transformed into Nagios host and Nagios service through a mapping file. |
Table of contents
Contributors
No contributors found for: authors on selected page(s)
|
Installation
These integration of Petals ESB, Petals CLI and Nagios is available on Debian-based system and is packaged as a Debian package: petals-cli-cmd-monitoring-so-nagios.
To run on other operating system, we need your contribution to port the daemon script wrapping Petals CLI on this operating system. |
See [Installing Petals CLI using the Debian packages] to get more information on this Debian package.
Configuration
Once your Nagios installation is configured to accept external commands, you must verify in /etc/petals-cli/petals-cli-nagios that the expected Nagios pipe file is set according to your Nagios installation. The default value is the one associated to the Debian package of Nagios.
To add a new defect subscription to sent to Nagios:
- create a new file in the directory /etc/petals-cli/nagios-subscriptions-available from the template /etc/petals-cli/nagios-subscriptions-available/nagios-subscription-template:
# JMX connection information to the Petals ESB container # host=localhost port=7700 username=petals password=petals # The subscription object and its arguments # subscription-object=petals-bc-soap extra-args=-n petals-bc-soap -t file:///etc/petals-cli/nagios-mapping-rules.properties
where the first part is the required JMX connection information to establish a communication with a Petals ESB container, and the second part is dedicated to the wanted defect.
- configure the file /etc/petals-cli/nagios-mapping-rules.properties to map the hosts and services declared into Nagios with your Petals ESB installation,
- you can test your defect subscription using the script /usr/bin/petals-cli-nagios:
> sudo /usr/bin/petals-cli-nagios <your-defect-subscription-file>
- once your defect subscription is working, just create a link into the directory /etc/petals-cli/nagios-subscriptions-enable, and restart the service petals-cli-nagios.
Supported defects
Components
Petals BC SOAP
The defects of the BC SOAP are supported by the subscription object 'petals-bc-soap'.
The defect emitter identifier is based on the template: <component-id>@<hostname>, where <component-id> is the JBI identifier of the BC SOAP sending the defect from the Petals ESB container running on <hostname>.
The following defects can be notified:
Defect | Identifier |
---|---|
HTTP thread pool exhausted | org.ow2.petals.bc.soap.httpserver.threadpool.exhausted |
Web-service client pool exhausted | org.ow2.petals.bc.soap.serviceclientspool.exhausted |