Page History

...

The JobScheduler Interface Monitor can be used to monitor the messages for the 3 use cases:

• error case
  • an error has occured occurred / been recovered during a job chain / job execution
    • the service_name_on_error setting is responsible for this monitoring case
• success case
  • a job chain / job ends succesfullysuccessfully
    • the service_name_on_success setting is responsible for this monitoring case
• performance check (see Timer)
  • usually the service_name_on_error setting is responsible for this monitoring case but the performance check will also work if only the service_name_on_success setting has been defined.

...

• attributes service_name_on_error and service_name_on_success
  • at least one of these attributes must be configured
  • both attributes can be configured together
  •  the use of this settings must be unique within one SystemNotification
    
    

NotificationMonitor supports the following attributes:

...

<!-- Example 
op5 NSCA Status: 
0 - OK 
1 - WARNING 
2 - CRITICAL 
3 - UNKNOWN --> 
... 
<!-- Sending occurred errors as CRITICAL (default) --> 
<NotificationMonitor service_name_on_error="JobScheduler Monitoring Errors"> 
... 
<!-- Sending occurred errors as WARNING --> 
<NotificationMonitor service_name_on_error="JobScheduler Monitoring Errors" service_status_on_error="1"> 
...

...

...

...