8.3.4.4 Sample Alert Purge Processes

This section includes three examples of the Purge Alerts process based on input parameters. In these examples, the process executes two jobs: numbers 300000 and 300001, which relate to scenario numbers 300000 and 300001, respectively. As a result of this job, the process creates 50 matches and nine alerts, and performs nine actions.

The following table defines the matches that relate to these alerts and actions:

Table 8-4 Example of Matches and Alerts Associated with Purge Alerts

MatchID Range Job ID/Scenario ID AlertID/Status Actions/Type/Date
300000-4 300000/300000 None None
300005-9 300000/300000 300000/OP None
300010-14 300000/300000 300001/OP 300000(OP) on 11/6/2006
300015-19 300000/300000 300002/NW

300001(OP) on 11/6/2005;

300002on 11/6/2006 (NW)
300020-22 300000/300000 300003/OP None
300023-24 300001/300001 300003/OP None
300025-27 300000/300000 300004/OP 300003(OP) on 11/6/2006
300028-29 300001/300001 300004/OP 300003(OP) on 11/6/2006
300030-32 300000/300000 300005/NW

300004(OP) on 11/6/2005 and

300005 on 11/6/2006 (NW)
300033-34 300001/300001 300005/NW

300004(OP) on 11/6/2005 and

300005 on 11/6/2006 (NW)
300035-39 300001/300001 300006/OP None
300040-44 300001/300001 300007/OP 300006(OP) on 11/6/2006
300045-49 300001/300001 300008/NW

300007(OP) on 11/6/2005;

300008on 11/6/2006 (NW)

Note:

While the Action ID values are not in time-order, their impact on the example above is negligible. The key aspects of the actions relevant to the discussion are the dates of the actions.

As a result, a range of matches is associated either wholly or partly with an alert, and a range of actions taken on the alerts, from either one job and associated scenario, both jobs and their associated scenarios, or the other job and scenario.

The sample Alert Purge Utility output explains the following situations: