System Monitor events

System Monitor handles two types of events: Run now and Out of connections.

  • Run now. You can trigger this event from the System Monitor page (Management > Administration > System Monitor) by selecting Run Now.
  • Out of connections. This event is triggered automatically when the system runs out of connections. When this happens, the system becomes unresponsive and you cannot trigger the Run now event manually.
When any of the two events is triggered, each node from the clustered environment (only one if WorldServer is not clustered) will do the following:
  1. Runs four thread dump collections. You can use them to determine which program threads are blocked, if any.
  2. Runs four spGetCurrentQueries collections. You can use them to associate database transactions with program threads.
  3. Runs all database stats: spGetBlockedSessions, spGetLockedObjects, spGetSessions, spGetCurrentQueries, spGetQueryStats. You can use these reports to identify blocked transactions and to get additional information about the slowest queries. The reports are generated as .html files.
  4. Uploads previous logs plus existing System Monitor logs to AIS or AWS, according to your configurations. These logs contain a timestamp and an event type name, so that you can distinguish between them.

Steps 1 and 2 are executed with a default delay of 10 seconds. The default value of the heartbeat polling interval is of 30 seconds. Therefore, the System Monitor reports should be available in two to five minutes. If you select Upload logs to AIS, the report should be available in Explorer at the following location: <AIS path>/SystemMonitor<node_name>/<system_monitor_report_name>.

If WorldServer runs in a clustered environment, there should be a System Monitor report for each node. However, in this case, only the master node contains the database stats reports.