A Petals ESB container is composed of several internal components. Each one can be monitored and provides several metrics:
* the transporters:
** the local transporter:
*** delivered messages

Each metric provides:
* a simple usage is based on a Cacti's data input method based on a Petals CLI command,
* a queried usage is based on a Cacti's data query invoking a Petals CLI command.

h1. Monitoring the transporters

h2. Monitoring the local transporter

h3. Delivered messages

|| Name || Description || Type ||
| Active | Number of delivered message with status 'Active' | COUNTER |
| Done | Number of delivered message with status 'Done' | COUNTER |
| Error | Number of delivered message with status 'Error' | COUNTER |
* by message exchange status and filtered for a dedicated endpoint, or a service, or an interface, see [Creating a graph using a data query|How to create a graph with Cacti#Creating a graph using a data query]
The local transporter provides a metric about the delivered messages that it delivers. This metric can be used simply to get the delivered messages by message exchange status whatever the endpoint, the service and the interface:
!petals-local-transporter-delivered-messages.png|align=center!
Or, through a queried usage to get the delivered messages to a dedicated endpoint/service/interface, by message exchange status.