Introduction

• System Monitors are tools that execute repeated checks for the availability of software components. 
  • For example, Nagios® is an Open Source System Monitor that is available at http://www.nagios.org.
  • An ecosystem of more or less compatible System Monitors has evolved, e.g. op5®, Checkmk and many others.
• Users can monitor JS7 with both Open Source and commercially licensed products to check the availability of the JOC Cockpit, Controller and Agents..

Active Checks and Passive Checks

• Active Checks are initiated from the System Monitor server and are performed on a regular basis, e.g. every 5 minutes.
  • The purpose of Active Checks is to verify the availability of the JS7 components.
  • Active Checks make use of the JS7 - REST Web Service API. For efficiency the checks are implemented with Perl.
• Passive Checks are initiated from the JOC Cockpit and report execution results of workflows and jobs to a System Monitor.
  • This mechanism is by far more accurate and efficient than polling the JS7 History for failed workflows and jobs.
  • The JS7 - Notification can be used for management of complex Passive Checks that are forwarded to a System Monitor.