Manage Audit Logs

When you execute multiple repeated publish jobs, the logs in the CA TDM Service audit table can use up the available memory space quickly. By default, CA TDM Portal truncates some of the audit information to save space. Watch this page to be notified about updates to audit log management functionality of .
tdm40
When you execute multiple repeated publish jobs, the logs in the CA TDM Service audit table can use up the available memory space quickly. By default, CA TDM Portal truncates some of the audit information to save space. Watch this page to be notified about updates to audit log management functionality of
Test Data Management
.
Enable Full Audit Log
As a Test Data Engineer for CA TDM Portal, you can enable the full, untruncated audit log. 
Follow these steps:
  1. Navigate to the directory where you installed the CA TDM Portal, and open the
    conf
    subdirectory.
  2. Locate and open the
    application.properties
    file in a text editor.
  3. Configure the log level to control memory usage.
    WebLogFullDetail = true|false
    • false
       — The audit log does not include full details, which saves space. API request/response messages in the audit log are truncated to 30 characters. This is the default.
    • true
      — The audit log includes full details of the request/response messages. 
      With full logging enabled, you may encounter issues with memory in the gtrep, as the log files can grow very big. As a Test Data Engineer for CA TDM Portal, set up a cleaning task on your database to regularly manage and clean table gtrep_web_log in gtrep. You will need to do this in accordance with your country’s legal requirements.