...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
... <!-- zabbix_sender Zabbix sender installed on the JobScheduler host localhost Hostname of the zabbix server Zabbix_server JobScheduler Agent name(host name) that registred on Zabbix samples.job1 Item key of zabbix (replace "/" to "." of JOB_NAME %MON_N_ERROR_TEXT% See explanation "Table variables" --> <NotificationCommand> <![CDATA[zabbix_sender -z localhost -s zabbix_server -k samples.job1 -o %MON_N_ERROR_TEXT%]]> </NotificationCommand> ... |
JobScheduler - Job Chains
Status colour Yellow title work in progress
| colour | Yellow |
|---|---|
| title | work in progress |
...
JobScheduler - Job Chains
Job Chains for these solutions have to be placed under \live\notification. Four Job Chains were implemented for this solution and they have the following functions:
CheckHistory: reads JobScheduler database tables where the logging is placed, analyses them and writes results into another tables, the Notification tables.CleanupNotifications: deletes entries in the Notification tables. Currently this takes place once every day.ResetNotifications: sets Status for Notifications in the Notification tables (e.g. Acknowledge)SystemNotifier: responsible for notifiying the system Monitor about the current notifications. Moreover, this JobChain is responsible for updating the Notification tables after having notified the System Monitor.
System Monitor
- The System Monitor receives just passive checks, that means, there are no active checks for monitoring JobScheduler. The only configuration here is the capability to receive passive checks from a remote host.
- The services in the System Monitor have to be in concordance with the JobScheduler configuration. Passive checks (services) have to be configured and named following the convention used in the XML described above for the JobScheduler (CheckHistoryConfiguration.xml and SystemMonitorNotification_op5.xml).
...
Use Cases
Recoverable Errors
...