Page History
Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
The JITL MonitoringJob RunReportJob template can be used to perform health checks of JS7 JOC Cockpit, Controller and Agents. Health check results can be forwarded, for example by mail.
- Users can use health status results for integration with their monitoring system.
- SOS offers a 24/7 Monitoring Service to receive health status results 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:
to automate execution of JS7 - Reports.
- Users can create monthly, weekly etc. reports.
- Users can schedule the creation of reports.
- repeatedly run the MonitoringJob template using a JS7 - Cycle Instruction,
- forward health check results to a monitoring solution.
- When used with a user's monitoring solution, this can include forwarding health check report files. This can include sending e-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.
- Alert mails are simplistic like this
The job template makes use of the JS7 - REST Web Service API to retrieve information run reports from the JOC Cockpit.
- The job template authenticates with the JS7 - REST Web Service API with a user account/password and/or with a certificate, for details see JS7 - Authentication.
- For details about configuration items see JS7 - JITL Common Authentication.
Display feature availability | ||
---|---|---|
|
Usage
When defining the job either:
- invoke the Wizard that is available from the job properties Job Properties tab in the Configuration view and select the JITL MonitoringJob RunReportJob Job Template and relevant arguments from the Wizard
or
- specify the
JITL
job class andcom.sos.jitl.jobs.monitoringrunreports.MonitoringJobRunReportJob
Java class name and add required arguments.
Example
...
- ..
Arguments
Name | Description |
---|---|
report_paths | List of paths pointing to the location of report configurations for which reports should be created Items in the list are separated by semicolon. Reports will be created for all list items. List items for non-existing report configurations will be ignored. If the same report configuration is specified more than once, then it will be used just once. If both |
report_folders | List of folders holding report configurations for which reports should be created Items in the list are separated by semicolon. Reports will be created for all list items. List items for non-existing report configurations will be ignored. If the same report configuration is specified more than once, then it will be used just once. This can occur if a report configuration is found in the Folders will be processed recursively if the name ends with: If both |