Monitor the eventin and eventout dbdicts

Monitoring eventin or eventout records is mainly to ensure the number of records is small and not constantly increasing. Old records should be reviewed because they are artifacts of failure, and then removed.

If the number of eventin records is large, verify that the event background scheduler is running and not hanging. As a large number of eventin records means large load, the idle time is expected to be 00:00:00. So it is important to understand whether it is running well or hanging under this load (see Monitor the schedule dbdict and background schedulers).

If Service Manager requires a longer time to process an event, the external application sending the eventin record may time out and resend the request. Service Manager is then completing the initial request and the resent one, and then causes another timeout. Depending on the timeout or resending configuration of the external application, this may increase the load for the event background scheduler so much that it cannot handle it.

Related topics

Queue Monitoring tasks

Event Services

Eventin dbdict

Eventout dbdict