Page History

...

These variables can be used when the NotificationCommand calls the notification client - not directly but via a shell script that makes the logical implementation for sending the notification messages.

Table variables

...

All table variables (see Table variables explanation) are set as environment variables with the prefix:

• SCHEDULER_MON_TABLE_

e.g.:

• SCHEDULER_MON_TABLE_MON_N_ID
• SCHEDULER_MON_TABLE_MON_N_SCHEDULER_ID
• ...

Service variables

...

Name	Description
SCHEDULER_MON_SERVICE_NAME	Current service name. One of both element attributes: SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_error SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_success
SCHEDULER_MON_SERVICE_STATUS	Current service status. One of both element attributes or default: SystemMonitorNotification / Notification / NotificationMonitor / @service_status_on_error SystemMonitorNotification / Notification / NotificationMonitor / @service_status_on_success default CRITICAL error default OK       success
SCHEDULER_MON_SERVICE_MESSAGE_PREFIX	ERROR      error                            RECOVERED    error recovery                             TIMER             performance check
SCHEDULER_MON_SERVICE_COMMAND	Content of the SystemMonitorNotification / Notification / NotificationCommand after substitution

  

Code Block
language bash title Sample NotificationCommand Unix. Script file (/tmp/command.sh). collapse true
1) configured command in the SystemMonitorNotification_<MonitorSystem>.xml file <NotificationCommand><![CDATA[/tmp/command.sh]</NotificationCommand>   2) content of the /tmp/command.sh file #! /bin/sh # Note: "> /tmp/command_output.txt" is used to simulate the starting of the notification client # echo "$SCHEDULER_MON_SERVICE_NAME:$SCHEDULER_MON_SERVICE_STATUS:$SCHEDULER_MON_SERVICE_MESSAGE_PREFIX history id = $SCHEDULER_MON_TABLE_MON_N_ORDER_HISTORY_ID" > /tmp/command_output.txt

...