By default, AppManager keeps event information available for display indefinitely and stores the event information in the AppManager repository in event and event archive tables. Because this information can accumulate over time and put a strain on your resources, you should manage the archiving, purging, and removing of events carefully. For example, moving old events to event archive tables when events are closed or have been kept for a specified amount of time can help keep the consoles clear of unimportant information and save you time by dealing with these less severe events automatically.
QDB preferences in the Operator Console let you change the default period for keeping events available in the consoles and automate your event handling.
To change the setting for keeping event information:
Click File > Preferences in the Operator Console.
Click the Repository tab, then click Event in the Event options group.
Check Move aged events to archive tables in repository when.
Select an option to archive events based on status, severity, or a period of time. You can choose to archive events:
When an Event is closed
When an Event stays open status for a certain number of days
When an Event stays closed status for a certain number of days
When a Closed event severity is greater than a specific severity level
For more information on these options, consult the Help.
Select the time, in days, for purging archive events from the repository. You can choose to purge events:
When the archived Event has been kept for more than a certain number of days in the repository
When the Oldest events exceed number of records allowed in the repository
For more information on these options, consult the Help.
Click OK in the Preference - Event Options dialog box.
Click OK in the Preferences dialog box.