Cloudera Lakehouse Optimizer auditing configuration properties

Use the following properties to configure auditing for Cloudera Lakehouse Optimizer:

Table 1. Auditing configuration properties
Property	Description	Default	Example
`dlm.audit.enabled`	Enables or disables Cloudera Lakehouse Optimizer auditing. When set to `false`, audit events are not written.	`true`	`true`
`dlm.audit.fs.uri`	The Hadoop-compatible URI where audit log files are written. Override the default path for production deployments.	hdfs:///tmp/clo-audit-logs	`hdfs:///user/dlm/audit-logs`
`dlm.audit.publisher`	The audit publisher type. Only `fs` is supported.	`fs`	`fs`
`dlm.audit.push.interval.ms`	The interval in milliseconds at which buffered audit events are written to the audit log. Events can also be written when the buffer reaches capacity.	`600000` (10 minutes)	`600000`
`dlm.audit.fs.rollover.time.ms`	The time-based rollover threshold in milliseconds. When this interval elapses, Cloudera Lakehouse Optimizer starts a new audit log file.	`86400000` (24 hours)	`86400000`
`dlm.audit.fs.max.events.per.file`	The maximum number of audit events per file before rollover. Set to `0` to disable event-count rollover.	`65536`	`65536`
`dlm.audit.file.name.prefix`	The filename prefix for audit log files. Cloudera Lakehouse Optimizer appends a period and sequence number. Do not include a trailing period in the property value.	`clo-audit.log`	`clo-audit.log`
`dlm.audit.fs.file.permission`	The POSIX permission mode (octal) applied to each audit file on HDFS and local filesystems.	`775`	`775`
`dlm.audit.fs.dir.permission`	The POSIX permission mode (octal) applied to the audit base directory on HDFS and local filesystems.	`750`	`750`