...

• The Monitor Service is used to receive events about executions check execution results of workflows and jobs from any connected Controllers and to add them to the JS7 - HistoryMonitor.
• As a result the execution history and logs of orders and tasks becomes availableerrors and warnings that occur during workflow execution become visible with the GUI and can be forwarded by JS7 - Notifications. Due to the asynchronous nature of JS7 components this task is performed by a background service.

...

Monitoring

The Monitor Service inspects the execution history includes reporting information about workflows, orders and tasks of workflows and jobs including information such as start time, end time and execution result.

Execution Logs

The Monitor Service can be configured 

• to report about successful and failed workflows and jobs,
• to report about jobs running longer or shorter than expected.

Notifications

Notifications are forwarded based on monitoring results, for example to report failed workflow executions by e-mail.

More information is available from the JS7 - Notifications articleExecution logs are provided for orders and tasks. Log output is added to the reporting database and is accessible from the JS7 - History.

Interaction with Controller

The Monitor Service makes use of the JS7 - History Service connects to the Controller by use of to receive events about workflow execution from a Controller via the Proxy Service, see JS7 - System Architecture.

...

Should a Controller not be active or should the network connection to a Controller not be available then the History Service will repeatedly try to connect. This behavior continues for minutes, hours and days. The Monitor Service will accordingly receive events after successful reconnection of the History Service.

Should a fail-over or switch-over occur with a Controller then this does not affect the History Service that is automatically routed to the active Controller instance by use of the Proxy Service.

Behavior of the Controller in case of Outages

Should the History Service not be active and therefore not release events then such events will remain with the Controller and will fill-up its journal. Events include any log output that is created from jobs and workflow instructions. Users should make an assumption about the maximum duration of an outage of the History Service during periods of high job frequency. The Controller's journal will grow as large as allowed within the limits of the file system. Due to the fact that individual log output of jobs is included and that jobs are executed at individual frequencies we cannot give an estimate of the growth rate. However, reserving a few GB disk space for both the Primary and Secondary Controllers' journals is required.

...

The Monitor Service receives events from the active Controller instance accordingly.

Configuration

Location

• The "Settings" menu is available from the JOC Cockpit GUI.

...