Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Monitor Service is used to check the results of the 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 will become visible with in the Monitor view of the GUI and can be forwarded by JS7 - Notification. Due to the asynchronous nature of JS7 components this task is performed by a background service.

...

The Monitor Service can be configured configured:

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

...

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

More information is available from in the JS7 - Notification article.

Interaction with Controller

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

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

Behavior of the Monitor Service in case of Outages

Should If a Controller is not be active or should if the network connection to a Controller is not be available then the History Service will repeatedly try to connect. This behavior continues will continue 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 will not affect the History Service that which 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.

...

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