Introduction

All components based on the Petals Component Development Kit provide following metrics:

Table of contents

Contributors

No contributors found for: authors on selected page(s)

Monitoring the provider side

Unable to render embedded object: File (message-exchange-acceptor-pool.png) not found.

See Creating a graph using a simple data to graph the stats of the pool accepting message exchanges:

Script/Command of the data input method: petals-cli.sh -h <petals_host> -n <petals_jmx_port> -u <petals_jmx_user> -p <petals_jmx_password> -c -- monitoring -o petals-bc-soap -f http-thread-pool -- -n <petals-bc-soap-id> -r
If you have only one Petals BC SOAP installed on your Petals node, the input field petals-bc-soap-id can be replaced by its value

Output fields of the script/command:

Name	Description	Type
`HttpServerThreadPoolAllocatedThreadsMax`	The maximum number of allocated threads	GAUGE
`HttpServerThreadPoolAllocatedThreadsCurrent`	The current number of allocated threads	GAUGE
`HttpServerThreadPoolIdleThreadsMax`	The maximum number of idle threads	GAUGE
`HttpServerThreadPoolIdleThreadsCurrent`	The current number of idle threads	GAUGE
`HttpServerThreadPoolMaxSize`	The maximum size of the thread pool	GAUGE
`HttpServerThreadPoolMinSize`	The minimum size of the thread pool	GAUGE
`HttpServerThreadPoolEnqueuedRequestsMax`	The maximum number of requests that are enqueued waiting a thread to be processed	GAUGE
`HttpServerThreadPoolEnqueuedRequestsCurrent`	The current number of requests that are enqueued waiting a thread to be processed	GAUGE