...
The benefits of the new solution are:
- No changes have to be made Flexible implementation:
Changes to your existing JobScheduler configuration (Jobs, Job Chains, etc.) in order are not required to get this solution working. You add the Job Chains required for the monitoring but do not have to modify your current ones. - Monitor independence:
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. - Workload-independent:
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. - Clearly defined information flow:
This solution makes very detailed information available for allows the information to be made available to the System Monitors . JobScheduler logs very exactly and this information to be exactly configured. Detailed log information from monitored Job Chains can be sent as a Passive Check to the relevant Monitoring Service if required. - Error Prioritization
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. This feature allows the Service Desk to be able to set priorities immediately when, for example, recovering errors. It : 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
| 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. |
...
| File | Description |
|---|---|
SystemMonitorNotification_v1.0.xsd | The XML Schema file that defines which values are allowed in your XML files for the JobScheduler monitoring. That means, you just have to modify your |
SystemMonitorNotification_<MonitorSystem>.xml | Configuration file for each System Monitor.
|
|
| Configuration file for all System Monitors.
This file is optional and just has to contain contains the definitions of the |
...
| Element | Element description | Description |
|---|---|---|
NotificationMonitor | Once inside a Notification element | Specifies the System Monitor interface that is being used for messages: either by a Plugin Plug-in Interface or by command line invocation |
NotificationObjects | Once inside a Notification element | Specifies the JobChains Job Chain and the Timers Timer definitions |
SystemMonitorNotification / Notification / NotificationMonitor
NotificationMonitor support supports the following attributes:
Note:
- attributes
service_name_on_errorandservice_name_on_success- at least one of these attributes must be configured
- both attributes can be configured together
...