...
SystemMonitorNotification
can contain severalNotification
definitions for notification of error or success conditionsNotification
contain one NotificationMonitorNotificationMonitor
contains the configuration for delivery notifications to System Monitor and has the following attributesservice_name_on_error
(optional) - Service name to send of error/recovery messagesservice_name_on_success
(optional) - Service name to send of success messages if order is successfully completedservice_status_on_error
(optional) - Service status (e.g. CRITICAL or WARNING) to send of error messages. If not set - CRITICAL will be sendedservice_status_on_success
(optional) - Service status (e.g. SUCCESS) to send of success messages. If not set - OK will be sended
NotificationMonitor
can has one of the following elementsNotificationCommand
command line for calling of the extern script for system notificationNotificationInterface
calling API for system notification (currently for NSCA notifications). This Element has the following attributesservice_host
(required) - hostname for the host the notification are sent from (the way it is named at the System Monitor)monitor_port
(required) - port of System Monitor to receive notificationsmonitor_host
(required) - hostname of System Monitormonitor_encryption
(required) - specifies that the communication with the System Monitor is encrypted. NONE, XOR, TRIPLE_DES encryptions are available.
NotificationObject
contains the configuration of objects, which will be sended to System MonitorJobChains
(optional) - can contain severalJobChain
definitionsJobChain
(optional) - can contain severalJobChain
definitionsJobChain
has the following attributesnotifications
(optional) - Number of notifications for the same problem. By default - 1scheduler_id
(optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same databasename
(optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checkedstep_from
(optional) - Start Job node name for checkingstep_to
(optional) - End Job node name for checking
Timers
(optional) - can contain severalTimer
definitionsTimer
has the following elementsJobChains
(optional) - can contain severalJobChain
definitions for performance notificatioJobChain
has the following attributesnotifications
(optional) - Number of notifications for the same check. By default - 1scheduler_id
(optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same databasename
(optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checkedstep_from
(optional) - Start Job node name for checkingstep_to
(optional) - End Job node name for checking
<!--
For this concrete example and following the description from above (about the schema):
...