Purpose

• The Monitor Service is used to check execution results of workflows and jobs from any connected Controllers and to add them to the JS7 - Monitor.
• As a result errors 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 of workflows and jobs including information such as start time, end time and execution result.

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 article.

Interaction with Controller

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

For any subscribed History Service instance the Controller holds events occurring from JS7 - Order State Transitions and forwards them to the History Service. After any subscribed History Service instances received events and confirmed receipt by releasing events then the Controller will drop events from its journal.

Behavior of the Monitor Service in case of Outages

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. The Monitor Service receives events from the active Controller instance accordingly.

Configuration

Location

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

Configuration Items

• No configuration items are required.
• A number of configuration items can optionally be used.

TODO

Logging

• The Monitor Service logs general messages, warnings and errors to the joc.log file.
• More detailed information in addition is logged to the Main Log service-monitor.log file.
• In addition to the Main Log detailed debug information is logged to the Debug Log service-monitor-debug.log file.
• For details see JS7 - Log Files and Locations