190. Integration - Connectivity

Monitor Connecticity Inbox and Outbox to find stuck messages and also verify that Connectivity processes are executing normally.

Multiple Instances: Yes (per Inbox/Outbox)

Interval: Every 15 minutes (96 times per day)

Status

Expression

Critical

If (Connectivity processes executed last 30m != 2)

Description	The number of Connectivity DB Processes may depend on the number of active inbox/outbox in an installation.
Impact	Connectivity integration is not working.
Suggestion	Check in Solution Manager > Background Processing > Background Jobs > Database Processes, and check Connectivity parameters in system parameters.

Warning

if (Stuck inbox messages more than 30m > 0) or (Stuck outbox messages more than 30m > 0)

Impact	Connectivity integration is not working. Messages are stuck.
Suggestion	Check corresponding Background Job for connectivity class.

If not status Warning or Critical.

Unknown

Missing application response.

Metric & Service	Command line example
Stuck inbox messages more than 30m	java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -appowner=<value> -request=CONNECTIVITY_INBOX_ROUTING -wa=0 -do
Stuck outbox messages more than 30m	java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -appowner=<value> -request=CONNECTIVITY_OUTBOX_ROUTING -wa=0 -do
Connectivity processes executed last 30m	java -jar application-monitoring-metrics-cli.jar db -host=localhost -instance=<instancename> -user=ifsmonitoring -pass=<password> -appowner=<value> -request=CONNECTIVITY_DB_PROCESSES -oeq=2 -dc