HP Integrity NonStop H-Series - Manual (Page 74)

Using Event Analyzer
WVP Event Analyzer Plug-in User Guide V01 – 536989-001
- 74 -
Figure 60 Alerts shown in Event Details Screen
Figure 60 shows how clicking on the ‘Alerts’ menu item brings up a window showing the alerts thrown
by EA the next day to notify of the threshold breach on July 6. In this case, for example, the user sets
a threshold of 100 maximum events per day for SSID 257. As is seen from the alert text, on July 6,
there were 133 events which triggered EA to throw an alert notifying the user of this breach. (Note:
The generation time of this event will indicate the EACOLL scan of events. This could be either the
daily scan or the load of events).
[Back to TOC]
4-13-3 Considerations
 It is recommended that different alerts have different EMS Event numbers specified. Having
duplicate EMS Event numbers may cause incorrect display of events in the EMS Viewer.
 When using multiple collectors which may have events with same Owner.Subsystem,
multiple EMS events may be generated for a breached threshold. The alert thresholds are
checked for each of the specified collector and hence may result multiple EMS events.
Multiple EMS events for the same alert can also be generated when using the One-time
Load option if the collector list was changed since the last Daily Run.
 If One-time Load is done for a collector(s) for which data had already been collected, the
alert counts will be added on to.