Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Security
  5. Connection Management
  6. JDBC Client Configuration
  7. ODBC Client Configuration
  8. Access Control
  9. Logs
  10. High Availability
  11. Server Control
  12. Performance Tuning
  13. Troubleshooting
  14. Appendix A: Database Keywords

Administrator Guide

Administrator Guide

System Loggers

System Loggers

A system logger is a pre-defined logger node in the Management Console tree that logs Dynamic Data Masking Server, service, and rule events.
The Management Console tree contains userReplacement, auditTrail, and rootLogger system loggers. The system loggers use Rolling File appenders to create the audit trail, rule, and server logs. You cannot delete or move the system loggers or the appenders. You can edit the Max File Size and Max Backups properties of the system logger appenders, but you cannot edit the Type, Name, and File properties. If you edit a system logger appender, Dynamic Data Masking immediately reconfigures config.properties and saves the file.
You can add appenders to the system loggers to log the same information in different formats.
The system loggers create the following log files:
auditTrail.log
Logs changes made within the Management Console. The AT appender of the auditTrail logger creates the auditTrail.log file.
rule.log
Logs rules that the Rule Engine applies to incoming requests. In the Management Console, you can use the Log When Rule is Applied box in the
Edit Rule
window to specify whether an occurrence of the rule is logged. The UR appender of the userReplacement logger creates the rule.log file.
If multiple rule log files exist, Dynamic Data Masking appends each file name with a version number, such as
rule.log1
. Dynamic Data Masking stores 10 rule log files by default. Rule logs update cyclically and restart on
rule.log1
when the logs are full.
By default, each rule log file stores up to 20 MB of data for a total of 200 MB. You can configure file size and the maximum number of files in the UR appender.
In high transaction volume applications, specify additional rule logs carefully due to the increased overhead.
You can use the Log Loader utility to load rule.log data into an Oracle, DB2, Informix, or Microsoft SQL Server database. See
Informatica Dynamic Data Masking Log Loader
for information on the Log Loader utility.
server.log
Logs server records, events, and error messages for internal troubleshooting of the Dynamic Data Masking Server operations. The R appender of the rootLogger logger creates the server.log file.
If multiple server log files exist, Dynamic Data Masking appends each file name with a version number, such as
server.log1
. Dynamic Data Masking stores up to 10 server log files at a time. Server logs update cyclically and restart on
server.log1
when the logs are full.
By default, each rule log file stores up to 20 MB of data for a total of 200 MB. You can configure file size and the maximum number of files in the UR appender.

Sample Rule.log File

The following excerpt is from the rule log:
05/30 16:55:39,240 [MASK@ERP-1] INFO - Blocking Rule: Identify Blocked Statement (user message: This request has been blocked.) select * from customer Done by ClientInfo:[User=Admin, Host=__jdbc__, application=JDBC Thin Client] - SessionID=74,2834 - SYSTEM - Instance 1 05/30 16:57:29,156 [sapiens@ERP-1] INFO - None Rule: auditlog BEGIN DBMS_OUTPUT.DISABLE; END; Done by ClientInfo:[User=Admin, Host=ADMIN-THINK, application=C:\app\Admin\product\11.2.0\dbhome_2\bin\sqlplus.exe] - SessionID=73,763 - system - Instance 1

Sample Server.log File

The following excerpt is from the server log:
05/23 13:16:00,075 [pool-1-thread-1] INFO - Service started. 05/23 13:16:00,077 [main] INFO - Service DDM for DB2 started 05/23 13:16:00,077 [main] WARN - DDM for Oracle.configure: Invalid address provided: null:0 05/23 13:16:00,079 [main] INFO - Service DDM for Oracle started 05/23 13:16:00,116 [main] INFO - Server started. 05/23 13:16:00,198 [Thread-3] INFO - Service DDM for SQL Server started 05/23 18:36:43,989 [Thread-2] WARN - ProcessService: ProcessService: restarting process. 05/23 18:36:44,005 [Thread-4] INFO - Service DDM for SQL Server started

0 COMMENTS

We’d like to hear from you!