{section}
{column}

h1. Introduction

Cacti is a complete monitoring and graphing tool to present historical data coming from monitoring probes.


[Get more details about Cacti.|http://www.cacti.net/]

The integration of Petals ESB and Cacti is to get information about the JVM. This is done using SNMP probes.

{column}
{column:width=350px}

{panel:title=Monitoring Petals ESB with Cacti}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}

h1. Installation


h2. Cacti installation

The Cacti integration was experienced on a Linux distribution "Ubuntu Precise Pangolin (12.04)".

Cacti is available in version 0.8.7i through the default Ubuntu repository. So, just install the package "cacti" using the standard way.

h2. Enabling the SNMP agents of the Petals ESB JVMs
{include:Enabling the SNMP agent of a Petals ESB JVM}

h2. Cacti configuration

Import in your Cacti configuration the content of the attachment [^cacti_host_template_jvm_host.xml]
Next, create the following datasource from templates:
!ds.jpg|align=center!



Next, create your graphs from templates:
!graph.jpg|align=center!

h1. Monitoring

!petals-container-localtransporter-dim.jpg|align=center!
Cacti monitoring extension of Petals CLI is used to get metric values.
In the *Input String*, you will put the command line arguments to connect to the the Petals node for which you want to graph the delivered messages of the local transporter. That's why the command line contains: *<petals_host>*, *<petals_jmx_port>*, *<petals_jmx_user>* and *<petals_jmx_password>*.
# Add an *input field* for your Petals node hostname
!petals-container-localtransporter-dim-petals-host.jpg|align=center!
As the Petals node hostname can be automatically set from the hostname of the monitored host, the field *Special Type Code* is set.
# Add others *input fields*
!petals-container-localtransporter-dim-petals-jmx-port.jpg|align=center!
As for the JMX port, create an input field for the Petals JMX username and the Petals JMX user password.
# Add the *output fields* returned by the script
For each message exchange status "Active", "Done" and "Error", create an output field:
!petals-container-localtransporter-dim-output-active.jpg|align=center!
# Check that you have the following *Data Input Method*:
!petals-container-localtransporter-dim-full.jpg|align=center!
# Create a new *Data Template*:
!petals-container-localtransporter-dt.jpg|align=center!
Select your data input method previously created as *Data Input Method*.
Add your first *data item* associated to the number of delivered messages for message exchange status 'Active'. The *data source type* of the item is *COUNTER*.
# Create two others *data items* associated to the number of delivered messages for message exchange status 'Done' and 'Error'
!petals-container-localtransporter-dt-items.jpg|align=center!
# A new block *Custom data* appears, check *Use Per-Data Source Value* for all except for the Petals node hostname
!petals-container-localtransporter-dt-custom.jpg|align=center!
# Create a new *Graph Template*:
!petals-container-localtransporter-gt.jpg|align=center!
# Add a *Graph Item* to displayed graph the number of delivered messages for message exchange status 'Active'
!petals-container-localtransporter-gt-active.jpg|align=center!
# Add a *Graph Item* to displayed the legend of the number of delivered messages for message exchange status 'Active'
!petals-container-localtransporter-gt-active-legend.jpg|align=center!
# Add others *Graph Items* associated to the number of delivered messages for message exchange status 'Done' and 'Error'
!petals-container-localtransporter-gt-full.jpg|align=center!
# Create a *New Graph*
!petals-container-localtransporter-ng.jpg|align=center!
# Set parameters needed to the *Data Input Method*
!petals-container-localtransporter-ng-params.jpg|align=center!