Environment
NetIQ AppManager 7.0.x
Situation
Resolution
AppManager doesn't take averages when generating Events. Whenever the conditions are met, the Event appears.
However, there are preferences for Knowledge Script advanced options that could be useful:
Event options
These options apply when Event is set to y in the Values tab on the Job Properties dialog. The options in this group control when an event is raised, based upon a specified number of event occurrences during a specified number of job iterations. If a duplicate event is raised, use these options to either collapse duplicate events or automatically close the original event when the event condition no longer exists.
Collapse duplicate events into a single event
Select to have duplicate events collapsed into a single event. An event is considered a duplicate when a recent Open child event with the same object name, event message, severity, and Job ID as a previous event occurs. Just like unique events, duplicate ones are logged in the repository and, if event collapsing is not enabled, are listed as additional child event entries under the parent event. Actions, if specified, are initiated for each duplicate event. With event collapsing enabled, instead of creating new child event entries, the duplicate events are collapsed into the original child event and the child event count is increased. The duplicate events are logged in the repository; however, actions associated with collapsed duplicate events, whether the actions are initiated on the managed client or management server, are suppressed.
Time interval for event collapsing
Set the time interval in minutes for collapsing duplicate events into a single event. The default is 20 minutes. This time period is fixed. For example, assuming a 20 minute time interval, events at 12:00 and 12:19 will be collapsed into a single event, while events at 12:00 and 12:21 will be raised as separate events. This option is useful to raise events at specific intervals until you are able to address the situation (in the case of the above example, one event every 20 minutes).
Time interval measured from...
Select an option to specify when the time interval for event collapsing begins:
Initial occurrenc e. This option sets the time interval to a static period of time that begins when the first event occurs. For example, using the default time of 20 minutes, the 20 minute interval is always restarted every 20 minutes.
Most recent occurrenc e. This option restarts the time interval for event collapsing each time an event is raised (the event collapsing interval is not a static period of time). For example, using the default time of 20 minutes, if a job generates duplicate events every five minutes, then the event is collapsed and the 20 minute interval is restarted every five minutes, which means it never effectively expires unless you set an option to have events ignored.