7.5 Managing Audit Trails

For security reasons, AppManager automatically collects audit information about when computers are placed in maintenance mode and about user logon activity. You can also configure AppManager to collect an audit trail for jobs, events, or actions using the Miscellaneous repository preference.

If you enable auditing for jobs, events, or actions, AppManager records information about every related operation in the repository. For example, if you enable auditing for job-related operations, the audit trail includes chronological information about who started each job, changes to job properties, and changes to job status.

Because the QDB stores audit information and can increase in size continuously, you should periodically remove the information that you no longer need from the tables that store the audit information you collect:

Table

Type of information stored

ActionHistory

Action-related activities

EventHistory

Event-related activities

JobHistory

Job-related activities

MachineMntHistory

Maintenance mode activity

Logon and logoff activity

Whether you choose to enable auditing for jobs, events, or actions, you should plan for periodic maintenance of the MachineMntHistory and QLogonoffHistory tables. For example, you should plan a regular backup strategy for saving historical information and establish a policy for manually removing audit information after a certain period of time.

NOTE:Do not remove information from the KSHistory table. The QDB manages the contents of this table internally.