ALM auditing
This section describes how ALM auditing works.
What to log and where logs are stored
The following table describes which actions are logged by ALM and where they are logged.
What to log | Where the log is stored | Notes |
---|---|---|
User operations that include:
|
In the AUDIT_LOG file |
|
Who cleared history and when | In the AUDIT_LOG database table | |
Changes to test steps (both design steps and run steps) | In the AUDIT_PROPERTIES and AUDIT_LOG database tables |
To enable the auditing for test steps:
Caution: We recommend that you do not enable the auditing for test steps unless it is necessary, as it generates a large amount of auditing data, especially for run steps. |
Both old and new groups for a user when its membership is changed | In the AUDIT_LOG file | |
Add fields to store the current user, the current project session ID, and the current user session ID | In the AUDIT_LOG file |
AUDIT_LOG file location
By default, the AUDIT_LOG
file is stored in the {ALM_deployment_folder}\log
directory.
You can use the AUDIT_LOG_PATH
parameter to specify a different location for the log file. In the new location, the log file is renamed AUDIT_LOG_<machine_name>
. For details about setting site parameter, see Set configuration parameters.