...
- There is no changes to be done in your JobScheduler configuration (Jobs, Job Chains, etc.) in order to get this solution working. You have to add the corresponding Job Chains for the monitoring but do not have to modify your current ones.
- The whole architecture lies at JobScheduler side and the solution is then independent from 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 in sense of performance nor in sense of stability.
- The level of detail in a message of a Service in the System Monitor is much higher with this solution. JobScheduler logs very exact what the error is about and this information is sent as a passive check to the specific Service, which shows the log message that JobScheduler logged.
- The criticality of an error is immediately recognized in the System Monitor. JobScheduler has all information about errors and this information is sorted out and sent to different Services in the System Monitor for every specific case. Through this feature, the Service Desk is immediately able to set its priority for recovering errors. For example, it does not have the same Criticality to recover an error of Performance (low) than when Documents could not be generated (high). Here you go a representation of this feature:
Functionality
| Functionality | Description |
|---|---|
| Job Chain and Order Monitoring |
...
| Job Chains in JobScheduler can be with the new solution monitored. Actually, the elements that are monitored are the Orders that trigger these Job Chains. | |
| History Notifications |
...
| Not only critical alerts are monitored, but also the positive ones. The history of a specific service is also monitored, to see exactly if a specific workflow was executed or not and what result it ended up with. |
...
| Performance measurement (Timer) |
| There are also Timers that measure the performance of a Job Chain. In case it takes too long for a Job Chain to end, a critical alert will be sent to a System Monitor. |
| Acknowledgment |
...
| Once a service in the System Monitor is critical, there is the possibility to acknowledge this service. That action will add an Order to the JobScheduler, so that JobScheduler does not send more notifications to the System Monitor for this service. |
Installation
See https://kb.sos-berlin.com/x/fYEm
...
JobScheduler - SystemMonitorNotification files
Location: <scheduler_install>/config/notification
| File | Description |
|---|---|
| SystemMonitorNotification_v1.0.xsd | XML Schema file that define 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.
|
| SystemMonitorNotificationTimers.xml | Configuration file for all System Monitors. This file is optional and can contains only definitions of the |
SystemMonitorNotification Elements
...