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

User operations that include:

  • Creating or deleting user
  • Editing user details
  • Adding users to projects
  • Removing users from projects
  • Adding and removing admin permission
  • Deactivating and activating users
  • Adding users to user groups
  • Ending user's project sessions
  • Ending user sessions
  • Creating or deleting user groups
  • Changing user password
  • Authenticating login username and password
  • API Key creation failures

In the AUDIT_LOG file

Who cleared history and when In the AUDIT_LOG database table
Changes to test design steps In the AUDIT_PROPERTIES and AUDIT_LOG database tables
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
IP addresses for all users connected to ALM In the AUDIT_LOG file
Changes to workflow scripts In the AUDIT_LOG file
Entity relations In the AUDIT_PROPERTIES and AUDIT_LOG database tables

Back to top

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 Setting ALM Configuration Parameters.

Back to top