...
- Some System Monitors may provide an "acknowledge" operation, that signals that a problem is known and that no further notifications should be sent by JobScheduler.
- Should an "acknowledge" operation have been performed for a specific service in the System Monitor then this job chain would stop JobScheduler from sending notifications to that service for errors that have already occurred.
- Order
AcknowledgeMonitorSystem- do not configure the order run time as this job chain will be triggered by the System Monitor operation "acknowledge".
Examples
Example ResetNotifications
...
add_order
The following example shows the XML command sent from a monitoring system to the JobScheduler to call the sos/notification/ResetNotifications job chain and set the relevant service name as acknowledged.
...
| Element | Attribute | Value | Description | |
|---|---|---|---|---|
| add_order | XML Command to add the new order to the specified job chain on the JobScheduler. | |||
| job_chain | sos/notification/ResetNotifications | Job chain path must correspond with the path of the ResetNotifications job chain installed on the JobScheduler. | ||
| id | Order identifier. | |||
| title | Order title. | |||
| param | 3 following parameters must be set: | |||
| name | service_name | JobScheduler Monitoring Error | Relevant service name to set all already occured service errors in JobScheduler Interface Monitor as acknowledged. | |
| name | system_id | op5 | System identification. Corresponds with | |
| name | operation | acknowledge | Fixed value. Operation name to execute the acknowledgement in the JobScheduler Monitoring Interface. |
Example ResetNotifications OP5 add_order perl
This example shows the integration of a Perl script into OP5 op5 monitor system that automatically sends the above XML command to the JobScheduler sos/notification/ResetNotifications job chain.
...
- Contact "acknowledgment" + Event Handler:
- it first of all requires a contact, that receives the Notifications in the same way as the other contacts. However, an event notification for this contact is not received via Mail but an Event Handler, i.e. an XML command will be executed instead of a mail being received. (Please see the next point, "
Notification Command".)
- it first of all requires a contact, that receives the Notifications in the same way as the other contacts. However, an event notification for this contact is not received via Mail but an Event Handler, i.e. an XML command will be executed instead of a mail being received. (Please see the next point, "
- The "svc_notify_ack_handle"
Notification Command:- this command will always be executed for the services that are specified for the contact. This command is executed when the service status changes (for example, by a change from
OKtoCriticalorAcknowledgmentof an Error). - The command executes a
check_acknowledge.plscript.
- this command will always be executed for the services that are specified for the contact. This command is executed when the service status changes (for example, by a change from
- The
check_acknowledge.plScript (see the example below): this script is executed by the command and first of all checks whether the command is a response to anAcknowledgment: - If the command is not a response to an
Acknowledgment: then nothing happens - If the command is a response to an
Acknowledgment: then the script causes the JobScheduler to be contacted and sent am XML query, that instructs the JobScheduler to start a specific job chain (thesos/notification/ResetNotificationschain)
...