For some event conditions, it is more useful to raise an event when AppManager first detects the condition and then raise a second event when the event condition stops. You can configure an AppManager job to do this; you can also choose to have AppManager close the first event automatically.
With the job you configured to raise an event when an event condition is detected and automatically close the original event when the condition no longer exists, AppManager creates a parent event and a child event with a status of open; if it detects subsequent duplicate event conditions, it suppresses additional child events and does not increase the event count. When the event condition no longer exists, AppManager creates a new event to indicate the change in the event condition and changes the status of the original event to Closed.
For example, the first time a job runs, an event condition does not exist; AppManager does not raise an event. The next time the job runs, AppManager detects an event condition and raises a parent event and a child event.
The job iterates several times, and each time the event condition exists—AppManager does not create additional child events and does not increase the child event count; there is only one child event in the Events tab of the List pane.
On the next iteration the job runs and AppManager does not detect the event condition. AppManager changes the status of the child event to Closed and creates a new informational event that indicates the change in the event condition status.
If you double-click the event that indicates the change in status of the event condition (for example, event 582), in the Event Properties window, the Message tab indicates that the original event (event 581) has been closed.
If the Knowledge Script job detects the event condition again, AppManager creates a new child event.
NOTE:
To automatically close an event when the original event condition no longer exists, configure the job to raise an event with a specified event severity level each time AppManager does not detect the event condition. This event is for informational purposes only and its event severity should be set accordingly. To prevent the parent event from having an Open status when the original event is closed, you can use the Operator Console to configure the QDB preferences to automatically close all open events based on severity level. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.
You can configure a job to either automatically close events when the event condition no longer exists or collapse duplicate events; you cannot do both. For information about event collapsing, see Section 6.8, What Are Duplicate Events?.
To configure an individual job to automatically close an event when the event condition no longer exists, you can do so from the Advanced tab in the Knowledge Script Properties dialog box. For more information, see Section 5.8.3, Automatically Closing an Event When the Event Condition No Longer Exists.
Use the Operator Console set global default options to automatically close events when the event condition no longer exists. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.
At this time, use the AppManager Operator Console to set global options for all jobs. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.