Configuring Notification-1
The following section describes how to configure the notification server to issue notifications that are sent through the AlarmPoint server.
Using the Custom Notification Type
To use AlarmPoint, you must use the custom notification event type when configuring the PATROL KM for Event Management rules.
Using AlarmPoint Notification Scripts
To integrate with AlarmPoint, use the following AlarmPoint notification scripts that are provided with PATROL KM for Event Management:
- AS_EVSLocalAlertNotifyAP.bat -- PATROL KM for Event Management notification script for Windows
- AS_EVSLocalAlertNotifyAP.sh --PATROL KM for Event Management notification script for Unix
Using PATROL KM for Event Management Notification Rules
The next step is to create PATROL KM for Event Management rules so that when a PATROL object enters an alarm state, the notification server calls the AlarmPoint notification script and passes a notification target that matches an AlarmPoint user ID. The rules you need are shown below:
- /AS/EVENTSPRING/ object / arsAction -- use this rule to specify that notification is enabled for the PATROL object.
- /AS/EVENTSPRING/ALERT/ object / alertLocalCommand -- use this rule to specify the path to the notification script on the notification server.
- /AS/EVENTSPRING/ALERT/CUSTOM/ object / customTargetsLocalALARM -- use this rule to specify the ID of the AlarmPoint user or user group. This rule is a local target rule, rather than a remote target rule, because the rule is located on the notification server and the notification server is performing the notification. Thus, notification is performed locally.
In these rules, objectrefers to a PATROL object, which can be an application class, an application instance, or a parameter. For example, a PATROL object could be the NT_CPU\CPU_0\CPUprcrProcessorTimePercent parameter.
| You can set these rules using the PATROL KM for Event Management or the PATROL Configuration Manager. The following topics describe how to set the rules using the PATROL KM for Event Management. For more information about using the PATROL Configuration Manager, see the PATROL Configuration Manager User Guide. |
Before You Begin
Before you set the notification rules, you must define notification servers and assign notification servers to the remote agents. For more information, see Configuring Notification Servers and Configuring Remote Agents.
To Set the arsAction Notification Rule
- From the PATROL console, access the managed system you are using as the notification server and display the KM menu commands as described in Accessing KM Commands and InfoBoxes.
- Choose the KM menu command Event Management > Alert Settings > Alert Actions > Set For Parameters.
- From the next series of dialog boxes, choose the application class, instance, and parameter. For example, NT_CPU\CPU_0\CPUprcrProcessorTimePercent. After you choose the desired parameter, the dialog box shown in the following figure is displayed.
SET EVENT MANAGEMENT VARIABLE:arsAction Dialog Box
- From the SET EVENT MANAGEMENT VARIABLE: arsAction dialog box, verify that the following options are selected:
- Trigger NOTIFY_EVENT (Perform Notification) - this option enables notification for the selected parameter.
- Make persistent (update config db) - this option ensures that any changes you make on this dialog box persist after an agent restart.
- To save your changes, click Accept.
The following configuration variable value is set to 4, which enables notification:
To Set the alertLocalCommand Notification Rule
- From the PATROL console, access the managed system you are using as the notification server and display the KM menu commands as described in Accessing KM Commands and InfoBoxes.
- Choose the KM menu command Event Management => Alert Settings => Local Alert Actions => Notification Command => Set For Parameters.
- From the next series of dialog boxes, choose the same parameter selected in the previous task: NT_CPU\CPU_0\CPUprcrProcessorTimePercent.
- From the SET EVENT MANAGMENT ALERT VARIABLE: alertLocalCommand dialog box, enter the full path name of the AlarmPoint notification script on the notification server computer. For example, /us/p/AS_EVSLocalAlertNotifyAP.sh.
- To save your changes, click Accept.
The following configuration variable is set as /us/p/AS_EVSLocalAlertNotifyAP.sh:
To Set the customTargetsLocalALARM Notification Rule
- From the PATROL console, access the managed system you are using as the notification server and display the KM menu commands as described in Accessing KM Commands and InfoBoxes.
- Choose the KM menu command Event Management > Alert Settings > Notification Targets > Custom > Local TargetsALARM > Set For Parameters.
- From the next series of dialog boxes, choose the same parameter selected in the previous task: NT_CPU\CPU_0\CPUprcrProcessorTimePercent.
- From the SET EVENT MANAGMENT ALERT VARIABLE: customTargetsLocalALARM dialog box, enter the ID of the AlarmPoint target, as shown in the following figure.
SET EVENT MANAGEMENT ALERT VARIABLES/RULES Dialog Box
- To save your changes, click Accept.
The following configuration variable is set as administrator:
When the NT_CPU\CPU_0\CPUprcrProcessorTimePercent parameter enters an alarm state on the notification server or on any remote agent configured to send events to the notification server, the notification server calls the AlarmPoint notification script and passes the AlarmPoint ID (administrator). The AlarmPoint script calls the AlarmPoint server, which notifies administrator according to his or her AlarmPoint user settings. For example, an e-mail message may be issued during the day and a page at night.