Sending Pages using AlarmPoint- Process Flow
The following diagram shows how a page is processed by the PATROL KM for Event Management. This process assumes the use of the enterprise notification software AlarmPoint. However, you can use any third-party paging software that has a command-line interface. The PATROL KM for Event Management rules associated with each step are shown:
Sending Pages using AlarmPoint Process
| Step | Description | Rule |
|---|---|---|---|
| |||
1. | Alert occurs on remote agent (parameter exceeds defined threshold and enters WARN or ALARM state, generating PATROL standard event 11 or 39) | NA | |
2. | Notification processing occurs on the remote agent as previously discussed in E-mail Notification Process. | arsAction | |
3. | The NOTIFY_EVENT is sent to the notification server.
|
| |
4. | The notification server process the REMOTE_NOTIFY_EVENT as previously discussed in E-mail Notification Process. | arsAction | |
5. | The notification server runs the script that calls the AlarmPoint Java client. |
| |
6. | The AlarmPoint java client sends the paging request to the AlarmPoint server. |
| |
7. | The AlarmPoint server processes the paging request and sends the page request to the paging device. The paging device could be a paging server, the internet, or whatever your enterprise is using for paging. |
| |
8. | The paging device sends the page to the defined target. |
|
