...

• Users can use health status results for integration with their monitoring system.
• SOS offers a 24/7 Monitoring Service to receive health status results of for customers using a commercial license and who subscribe to this support option, see JS7 - License.

The JITL MonitoringJob template can be used as a building block in a monitoring solution to:

• repeatedly running run the MonitoringJob template using a JS7 - Cycle Instruction,
• forwarding forward health check results to a monitoring solution.
  • this can include to forward health check report files when When used with a user's monitoring solution, this can include forwarding health check report files.
  • this This can include to send sending e-mail indicating mails containing a notice or an alert to SOS. Such notices do not include any data related to the user's JS7 environment, they only indicate a notice or alert only.
    
    • Alert mails are simplistic like this
    • 

...

• The job template authenticates with the JS7 - REST Web Service API by use of with a user account/password and/or by use of with a certificate, for details see see JS7 - Authentication.
• For details about configuration items see JS7 - JITL Common Authentication.

...

Using the Example

It is recommended to start from the example and to adjust is used as a starting point and that the parameterization is modified:

Explanation:

• A JS7 - Cycle Instruction is used in order to repeatedly perform health status checks.
  • Users should adjust cycles to their monitoring needs.
• A JS7 - Retry Instruction is used in order to retry execution, for example of the MailJob included in case that e-mail cannot be sent.
• The MonitoringJob is used to perform the health status check.
• The MailJob is used to send notices and alerts by mail. This is an option , - users might apply other means to forward notices and alerts.

...

• controller_id: Optionally specifies the identification of the Controller to be checked. By default the current Controller is used.
• monitor_report_dir: Specifies the directory to in which the job will store health status report files (.json). The directory has to exist prior to running the job and has to be in reach of the Agent that runs the job. 
  • An absolute or a relative path can be specified.
  • An expression can be used. The example makes use of env('JS7_AGENT_DATA') ++ '/monitor' which translates to use of the JS7_AGENT_DATA environment variable created by the Agent's start script, see JS7 - Job Environment Variables. The This environment variable can for example evaluate to /var/sos-berlin.com/js7/agent. The ++ operator indicates concatenation and is followed by the name of a sub-directory. In this example the report directory will be /var/sos-berlin.com/js7/agent/monitor.
• monitor_report_max_files: The number of report files created will be limited to this value. Older report files will be removed when this value is exceeded.
• from: Specifies the e-mail address that is used to send mail for notices and alerts. The argument is used by the job to create the subject and body return variables for use with a later MailJob.
• max_failed_orders: The maximum number of failed orders that are considered acceptable for a health status check. If this number is exceeded then the result return variable will carry a non-zero value indicating a failed health check.
• Select the check box provided with each argument if you want this argument to be added to the arguments of the MonitoringJob template.

...

The number of failed checks is reported by the result return variable, see next chaptersection.

Documentation

The Job Documentation including the full list of arguments can be found under: https://www.sos-berlin.com/doc/JS7-JITL/MonitoringJob.xml

...

...