Alert

The Alert system is designed to perform some sort of action based on a triggering mechanism. The alerting system requires data as an input, a decision on what data to act on, and a set of output actions. The triggering mechanism can be an agent or a scheduled request that is supplied some sort of data or goes out and gets some sort of data to act upon. This data can be filtered and the results used to trigger a set of actions. The actions are what can be done based on the rules of the triggering mechanism, such as send out an email, run stored procedure, run a batch job, etc. 

The most common action is to send out a message indicating something happened. For example, we can fire off a process every day that returns a list of employees that had poor performance below some threshold. Then for each of these, we can send out an email to a designated person indicating that employee’s performance. The recipient can also be required to acknowledge that he received the email, and if not, a second person can be notified in an escalation process.

Creating an Alert

To create an alert:

1. Subscribers must be created to know who will be notified.
2. Alerts must be configured to determine what action will be performed.
3. Agents must be configured to allow some sort of data input for the alert to be triggered.
4. Events must be configured to generate the data that can be used for alerting.
5. Event Scheduler must be configured to determine when the alert should be executed.

To access the Alerts screen:

1. Log in to ProTrack Warehouse.

2. Select Alert under the Configuration menu. The Alerts screen appears.
   
   
   ^{Fig.1 Maintain Alerts}

    

Acknowledging Alerts

To acknowledge a new alert:

1. Select the check box to the left of the alert.
   
   
   ^{Fig.2 Acknowledge Alerts}
2. Click . A popup will appear asking to confirm the alert(s) will be acknowledged. Click .
   
   
   ^{Fig.3 Confirm Acknowledging of Alerts}
    
3. The status of the alerts will be changed to Acknowledged.
   
   
   ^{Fig.4 Alerts Have Been Acknowledged}
   
   

Alert History

The Alert History screen is a listing of alert actions that have been executed, and their status, if any.  Every alert action, including wait and repeat, gets logged into history. If the action was an email, the email message gets saved. If the alert was an email requiring an acknowledgement, it will get logged with the status of acknowledged or waiting for acknowledgement. By clicking on one of the entries, you get a pop-up the more detailed information regarding the alert, such as when and who acknowledged an email action.


^{Fig.5 Alert History}