Command 'monitoring'

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (9)

View Page History
- service-provider-invokations-response-times: Response times of service provider invokations
- mex-acceptor-thread-pool: Message exchange acceptor pool statistics
- mex-acceptor-working: Statistics about working message exchange acceptors
- mex-processor-object-pool: Message exchange processor object pool statistics
- mex-processor-thread-pool: Message exchange processor thread pool statistics
- incoming-http-requests-count: Counters of incoming HTTP requests
- incoming-ws-requests-count: Counters of incoming web-service requests
- incoming-ws-requests-response-times: Response times of incoming web-service requests
- http-thread-pool: HTTP Thread pool statistics
- ws-clients-pools: WS-clients pools statistics
- outgoing-ws-requests-count: Counters of outgoing web-service requests
- outgoing-ws-requests-response-times: Response times of outgoing web-service requests
- generic: Generic monitoring for CDK based component
- service-provider-invokations-count: Counters of service provider requests
- service-provider-invokations-response-times: Response times of service provider invokations
- mex-acceptor-thread-pool: Message exchange acceptor pool statistics
- mex-acceptor-working: Statistics about working message exchange acceptors
- mex-processor-object-pool: Message exchange processor object pool statistics
- mex-processor-thread-pool: Message exchange processor thread pool statistics
- local-transporter: Message exchange local transporter
|| Object || Metric || Command line ||
| CDK-based component | [Message exchange acceptor thread pool|#message-exchange-acceptor-thread-pool] | {{-o generic -f mex-acceptor-thread-pool}} |
| CDK-based component | [Working message exchange acceptors|#working-message-exchange-acceptors] | {{-o generic -f mex-acceptor-working}} |
| CDK-based component | [Message exchange processor object pool|#message-exchange-processor-object-pool] | {{-o generic -f mex-processor-object-pool}} |
| CDK-based component | [Message exchange processor thread pool|#message-exchange-processor-thread-pool] | {{-o generic -f mex-processor-thread-pool}} |
{code}

h3. {anchor:working(message-exchange-acceptors}Working message exchange acceptors

Several metrics about the working message exchange acceptors of the component are available through the sub function '{{mex-acceptor-working}}' of the monitored object '{{generic}}'. It's usage is:
{code}
-n <component-name>
{code}
where '{{<component-name>}}' is the unique name of the JBI component with which it was deployed.
Returned metrics are:
* {{MexAcceptorWorkingNbMax}}, the maximum number of working message exchange acceptors since the last startup of the component,
* {{MexAcceptorWorkingNbCurrent}}, the current number of working message exchange acceptors,
* {{MexAcceptorWorkingDurationMax}}, the max duration of message exchange acceptor processing since the last startup,
* {{MexAcceptorWorkingDurationAvg}}, the average duration of message exchange acceptor processing since the last startup,
* {{MexAcceptorWorkingDurationMin}}, the min duration of message exchange acceptor processing since the last startup,
* {{MexAcceptorWorkingDuration10p}}, the 10-percentile duration of message exchange acceptor processing on the last sample,
* {{MexAcceptorWorkingDuration50p}}, the 50-percentile duration of message exchange acceptor processing on the last sample,
* {{MexAcceptorWorkingDuration90p}}, the 90-percentile duration of message exchange acceptor processing on the last sample,

{code}
> ./petals-cli.sh -h localhost -n 7700 -u petals -p petals -c -- monitoring -o generic -f mex-acceptor-working -- -n petals-bc-soap
MexAcceptorWorkingNbMax:20 MexAcceptorWorkingNbCurrent:0 MexAcceptorWorkingDurationMax:0 MexAcceptorWorkingDurationAvg:0 MexAcceptorWorkingDurationMin:0 MexAcceptorWorkingDuration10p:0 MexAcceptorWorkingDuration50p:0 MexAcceptorWorkingDuration90p:0
{code}

h3. {anchor:message-exchange-processor-object-pool}Message exchange processor object pool