Sending Notification- Process Flow
The following table shows how a notification is processed by the PATROL KM for Event Management when the notification server sends an e-mail notification. The same process applies to paging, trouble-ticket, or custom notification.
E-mail Notification Process
| Step | Description | Rule or Variable |
|---|---|---|---|
| 1. | Alert occurs on remote agent - parameter exceeds threshold and enters WARN/ALARM state, generating PATROL standard event 11 or 39. | NA |
2. | Recovery action initiated (if configured) | arsAction | |
3. | The remote agent triggers a PATROL NOTIFY_EVENT (if arsAction = 4 or 6) | arsAction | |
4. | CustomID values are set (if configured) | customId1 customId2 | |
5. | Notification message reworded (if configured) | msgText | |
6. | PATROL determines if a blackout period applies. If so, NOTIFY_EVENT is not sent to the notification server. | blackoutPeriod | |
7. | The alert is queued. | alertResetOnInit | |
8. | Determine whether notification is local or remote. If local, notification sent from remote agent. If remote, notification sent from notification server. | alertSystem
| |
9. | Determine the notification targets. | emailTargets | |
10. | Remote agent NotifiedEvent parameter is annotated with alert information. | NA | |
11. | A REMOTE_NOTIFY_EVENT is sent to notification server (if arsAction = 4 or 6) | NA | |
12. | The notification server parses REMOTE_NOTIFY_EVENT event details, which contains the same information as the original NOTIFY_EVENT. | NA | |
13. | Repeat steps 4 through 10 on the notification server (except step 7). | Multiple. See steps 4 through 10. | |
14. | The notification server runs the script to send e-mail message to targets. | emailTargets |
