...
- No changes have to be made to your existing JobScheduler configuration (Jobs, Job Chains, etc.) in order to get this solution working. You add the Job Chains required for the monitoring but do not have to modify your current ones.
- The whole architecture lies on the JobScheduler side and the solution is therefore independent of the monitor that the Alerts are sent to. The solution works for every monitor that can receive passive checks.
- Processing of Jobs and Job Chains in JobScheduler is not affected or modified by the monitoring, neither from the point of view of performance nor that of stability.
- This solution makes very detailed information available for the System Monitors. JobScheduler logs very exactly and this information can be sent as a Passive Check to the relevant Monitoring Service if required.
- Errors of a critical nature are immediately recognized in the System Monitor. The JobScheduler has initially access to all the log information and can be configured to filter this information very exactly before forwarding it to the relevant System Monitor Service. Through this This feature , allows the Service Desk is immediately to be able to set priorities immediately when, for example, recovering errors. It is unlikely that a performance error would be given the same priority as an error in document processing. This feature is illustrated in the following diagram:
...
| Functionality | Description |
|---|---|
| Job Chain and Order Monitoring | This solution allows Job Chains in JobScheduler to be monitored by way of the Orders that trigger these Job Chains. |
| History Notifications | Not only can critical alerts be monitored, but also positive ones. The history of a specific service can be monitored to see exactly if a specific work-flow has been executed and what result it gave. |
| Performance measurement (Timer) | Timers can be used to measure the performance of Job Chains. These can be used to send a warning alert to a System Monitor if a Job Chain takes more that a predefined time to complete. |
| Acknowledgment | Acknowledgments sent in response to critical alerts sent out by a System Monitor can be used to add Orders to the JobScheduler, so that the JobScheduler does not send more notifications about a service to the System Monitor. |
Monitoring
...
example - op5 Monitor
Here is an example of JobScheduler monitoring in The following example illustrates use of the JobScheduler Monitoring interface with the op5 Monitor. There are In the example, 3 checks (in op5 Monitor they are called services) have been defined for the JobScheduler monitoring. Different Job Chains in JobScheduler can send notifications to the same check, so that it is not necessary to create one check checks for each individual Job Chain, because that could produce a chaotic monitoringwhich could become extremely complex. Instead, we group results have been grouped in three categories:
- JobScheduler Monitoring Errors: Job Chains that end up with an error are sent to this service. The last error notification is shown in the column "STATUS INFORMATION".
- JobScheduler Monitoring Success: Job Chains that end up with success, that means, also positive notifications is with a positive notification, are sent to the monitoring system. ConcretelyTo be exact, the history of a specific Job Chain is also monitored , to see whether a specific workflow was work-flow has been executed or not. The last success notification is shown in the column "STATUS INFORMATION".
- JobScheduler Monitoring Performance: There are also timers that Here timers are used to measure the performance of a Job Chain. In case it If a Job Chain takes too long for a Job Chain to end, a warning alert will be sent to a the System Monitor. The information about the expired timer is shown in the column "STATUS INFORMATION".
Installation
See JobScheduler Monitoring Interface - Prerequisites and Installation
...