...
- will be sent:
- when at the time of the sos / notification / SystemNotifier run, an order is in a job chain state(step) that has ended with an error
- will not be sent:
- when after the last run of the sos / notification / SystemNotifier, an error has occured in an job chain state(step) but at the time of the current sos / notification / SystemNotifier run this order is in an other/next job chain state(step)
- this kind of error is ignored because the order has continued to run
- when an error has reoccurred in the same job chain state(step) where a notification has already been sent
- this order state is considered as notified and no new notification will be sent
- e.g. an job chain state(step) has been restarted manually or by a setback
- this behaviour has been changed with
- providing support for repeatedly failed executions.Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-534
- this order state is considered as notified and no new notification will be sent
- when the first step of the specific order has been removed from the notification tables by sos / notification / CleanupNotifications
- this behaviour has been changed with
- providing support for long running ordersJira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-516
- this behaviour has been changed with
- when a notification maximum has been reached
- when a job chain state(step) has been configured as excluded
- when the
@step_fromor@step_tosettings have been configured and the job chain state(step) is out of the configured range - when the
@return_code_fromor@return_code_tosettings have been configured and the return code of the job chain state(step) is out of the configured range
- when after the last run of the sos / notification / SystemNotifier, an error has occured in an job chain state(step) but at the time of the current sos / notification / SystemNotifier run this order is in an other/next job chain state(step)
Recovery messages
- will be automatically sent using the same service name and message as the relevant error message:
- when the error message of a job chain state(step) has already been sent and the order at the time of the current sos / notification / SystemNotifier run is in an other/next state(step)
- e.g. the rerun of the error state(step) has been successfull and the order has been moved to the next job chain state(step)
- Note: use
${SERVICE_STATUS}and${SERVICE_MESSAGE_PREFIX}variables to differentiate between recovery and error message
- when the error message of a job chain state(step) has already been sent and the order at the time of the current sos / notification / SystemNotifier run is in an other/next state(step)
- will not be sent:
- when a job chain state(step) has recovered after the last run of the sos / notification / SystemNotifier but at the time of the current sos / notification / SystemNotifier run a new error in the other/next step has occured
...
- will be sent:
- when a job chain state(step) or standalone job (JobScheduler versions from 1.12) ends with an error
- will not be sent:
- when a notification maximum has been reached
- when the
@return_code_fromor@return_code_tosettings have been configured and the return code of the job is out of the configured range
Notify on success
SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_success
...
- will be sent:
- when an order is completed and the last job chain state(step) has no error
- will not be sent:
- when a notification maximum has been reached
- when the
@return_code_fromor@return_code_tosettings have been configured and the return code of the job chain state(step) is out of the configured range
SystemMonitorNotification / Notification / NotificationObjects / Job
...
- will be sent:
- when a job chain state(step) or standalone job (JobScheduler releases from 1.12) ends without error
- will not be sent:
- when a notification maximum has been reached
- when the
@return_code_fromor@return_code_tosettings have been configured and the return code of the job is out of the configured range
Configuration Editor
We recommend that the XML Editor is used generate monitoring configuration objects. This editor automatically uses an XSD Schema to generate configuration suggestions and validate configurations, and its use is intended to provide a significant reduction in the time required to develop and test a configuration.
...
- JobScheduler releases before 1.11
- JobScheduler releases starting from 1.11
- Set param
sos.use_notification true (config/scheduler.xml) - see JobScheduler - Job Chains
- Set param
Note:
- JobScheduler releases before 1.13.1
SystemMonitorNotification_<MonitorSystem>.xml
- JobScheduler releases starting from 1.13.1
SystemMonitorNotification_<MonitorSystem>.xmlfile(s) (see below) must be configured before activtion or- The NOTIFICATION configuration was forwarded by the Joc Cockpit to the respective JobScheduler Master.
...
| Attribute | JobScheduler release | Usage | Description |
|---|---|---|---|
system_id | before 1.13.1 | required | System Monitor identifier. See JobScheduler - Job Chains customization Note:
|
| starting from 1.13.1 | required |
|
...
The Monitoring Interface provide functionality to store the job/order parameters of the specific jobs into database (table SCHEDULER_MON_RESULTS).
See explanation : Calculation
JobScheduler - Job Chains
...
SystemMonitorNotification_<MonitorSystem>.xml- Configure SystemMonitorNotification / Timer
- Configure SystemMonitorNotification / Notification / NotificationObjects / TimerRef
- Configure
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor)
System Monitor- Services in the System Monitor have to be configured and named the same way as in the
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor) above.
- Services in the System Monitor have to be configured and named the same way as in the
SFTP connection refused
...
SystemMonitorNotification_<MonitorSystem>.xml- Configure SystemMonitorNotification / Notification / NotificationObjects / JobChain for relevant Job chain.
- Configure
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor)
System Monitor- Services in the System Monitor have to be configured and named the same way as in the
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor) above.
- Services in the System Monitor have to be configured and named the same way as in the
Thresholds
Initial Situation
...
SystemMonitorNotification_<MonitorSystem>.xml- Configure SystemMonitorNotification / Notification / NotificationObjects / JobChain for relevant Job chain
- Configure
service_name_on_success(SystemMonitorNotification / Notification / NotificationMonitor)
System Monitor- Services in the System Monitor have to be configured and named the same way as in the
service_name_on_success(SystemMonitorNotification / Notification / NotificationMonitor) above.
- Services in the System Monitor have to be configured and named the same way as in the
Acknowledgment
Initial Situation
...
SystemMonitorNotification_<MonitorSystem>.xml- Configure SystemMonitorNotification / Notification / NotificationObjects / JobChain for relevant Job chain.
- Configure
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor)
System Monitor- Services in the System Monitor have to be configured and named the same way as in the
service_name_on_error(SystemMonitorNotification / Notification / NotificationMonitor) above.
- Services in the System Monitor have to be configured and named the same way as in the
Change Management References
...