Logs
TDM log files record events and tasks that the TDM Server and the Test Data Manager perform. You can configure log levels, log sizes, and archive settings for log files.
The TDM Server creates the following types of log files:
- Client logs
- Contain information about actions performed in the Administrator view of the Test Data Manager. The client logs also includes log information about login attempts and actions that users perform.
- The client logs are stored in the following location:
<Informatica installation directory>/TDM/logs/tdm.log
- Event logs
- Contain TDM Server events, including startup information for the TDM Server.
- The event logs are stored in the following location:
<Informatica installation directory>/TDM/logs/events.log
- Server logs
- Contain detailed information about all the actions that the TDM Server performs. You can find log information about user activities, such as the creation of rules and policies.
- The server logs are stored in the following location:
<Informatica installation directory>/TDM/logs/log.log
- Job logs
- Contain detailed information about all the jobs that the TDM Server performs. You can find log information about every job that a user performs in TDM.
- The job logs are stored in the following location:
<Informatica installation directory>/TDM/logs/jobLogs/job_<ID>.log
- Console logs
- Contain detailed information for all the jobs that the TDM Server performs. You can find log information about each job when TDM triggers a job. You can view the console logs even when the job logs are not present.
- The console logs are stored in the following location:
<Informatica installation directory>/TDM/logs/jobLogs/console_<ID>.log
- Profiling logs
- Contain detailed information for all the profiling jobs that the TDM Server performs.
- The profiling logs are stored in the following location:
<Informatica_Home>/tomcat/bin/disLogs
- Test Data Manager Service logs
- Contain detailed information for all the Test Data Manager Service startup, shut down, content creation, and content upgrade actions.
- You can access all the Test Data Manager Service logs from the Logs | Services view of the Informatica Administrator tool.
Log Configuration
TDM uses the logback logging system to perform logging for the TDM Server. You can configure log levels and the location of log files.
To configure log files, modify the log configuration file. The log configuration file is stored in the following location: <TDM Installation Directory>/configuration/serviceability.xml
The changes that you make to serviceability.xml take effect when you restart the TDM Server.
Note: You can find out more information about the logback logging system at the following site:
http://logback.qos.ch/ Log Levels
You can configure the level of logging for the client log, the event log, and the server log. You can set the severity levels for the TDM modules in Test Data Manager.
When you configure serviceability.xml, you can change the logging levels through the logger level property. If the log level for a particular log file is not specified, the TDM Server uses the value specified in the root level property as the log level.
The following table describes the log levels that you can set:
Log Level | Description |
|---|
ALL | Contains messages for all log levels. |
DEBUG | Indicates TDM Server operations at a detailed level. Debug messages generally record the success or failure of server operations. Debug messages have the lowest severity level. |
INFO | Indicates that the TDM Server is performing an operation that does not indicate errors or problems. Information messages have the second lowest severity level. |
WARN | Indicates that the TDM Server is performing an operation that may cause an error. Warning messages have the third highest severity level. |
ERROR | Indicates that the TDM Server failed to perform an operation or respond to a request from a client application. Error messages have the second highest severity level. |
FATAL | Fatal error occurred. Fatal error messages have the highest security level. |
TRACE | Indicates TDM Server operations at a more specific level than the debug logs. Trace messages are generally trace code paths. Trace messages have the lowest severity level. |
OFF | Turns logging off. |
Log Location and Archives
You can change the location where the TDM Server writes log files. You can also configure log file archiving.
When you configure serviceability.xml, you can configure archiving for the client log, event log, the server log.
The following table describes the properties that you configure for the log location and archiving:
Property | Description |
|---|
file | The file path for the log file with reference to the TDM installation directory. |
FileNamePattern | The file path and the naming convention for archived log files with reference to the TDM installation directory. Use the %i modifier archive files by number. Use the %d modifier to archive files by date. To save directory space, use .gz or .zip when you archive files. For example, you might specify the following file name pattern: <TDM installation directory>/serviceability/logs/tdm_%i.log.zip |
MaxFileSize | The maximum size for a log file. You can configure a file size in bytes, kilobytes, megabytes, or gigabytes. Default is 10 MB. |
MaxIndex | The maximum number of log files that the TDM Server will create. The TDM Server will not create more than 12 log files even if you configure a size greater than 12. Default is 4. |
Archive Example
Your organization wants to configure the archive specification for the server log, tdm.log.
You configure the maximum file size to be 8 MB, and you configure the maximum number of files to be seven. The TDM Server uses the following process to manage the server log:
- 1. The first time you start the TDM Server, it creates a file named tdm.log.
- 2. It continues to write to the file until the file reaches a size of 8 MB.
- 3. When the file reaches 8 MB, it renames the file to tdm_1.log.zip, and it creates another log named tdm.log.
- 4. When TDM.log reaches 8 MB, it renames tdm_n.log.zip to tdm_n+1.log.zip, and it creates another server log named tdm.log.
- 5. The TDM Server continues to rename the log files until it reaches the maximum index of seven, and it overwrites the oldest log file.
The following snippet of code shows the configuration for the server log.
Application Logs
Application logs record the internal errors that occur within Test Data Manager. Application logs do not contain any job-related logs.
Application logs contain the following severity levels: Debug, Info, Warning, and Error. View the application logs from the Application Logs tab. You can perform search, sort, and filter operations based on the date range, context, severity level, error description, and owner name. When you select an error message, the row expands to display the details of the error message. You can scroll down to 1000 lines to view the complete log. To refresh the log messages, click Refresh. To download the log file, click Download.