Integrations and print jobs might not be processed if Batch Processor is not running properly. This check will monitor if Application Messages is stuck in different states too long.
Multiple Instances: No
Interval: Every 30 minutes (24 times per day) - Due to full table scans
Status | Expression | ||||
---|---|---|---|---|---|
Warning |
If (Application Messages in state ’Released’ for 2h >
0) or (Application Messages in state ’processing’ for 2h
> 0) or (App server Batch Queues with Error > 0)
|
||||
OK | If not status Warning. | ||||
Unknown | Missing application response. |
Metric & Service | Command line example |
---|---|
Application Messages in
state ’Processing’ for 2h |
java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -request=APPL_MESSAGES_PROCESSING_2H -wa=0 |
Application Messages in
state ’Released’ for 2h |
java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -request=APPL_MESSAGES_RELEASED_2H -wa=0 |
App server Batch Queues
with Error |
java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -request=APPL_SERVER_BQ_WITH_ERROR -wa=0 |