16 Audit Data, Security, Artifact Changes, and LCM Events
Essbase auditing tracks changes to cube data, server-level security, LCM events, artifact changes, and MaxL statements that are run on the server, including imports.
Use cube-level data auditing to track updates made to data values, including changes to Linked Reporting Objects (LROs), such as adding notes, attaching files, and referencing URLs. You can export the audit log to an Excel spreadsheet.
Use server-level auditing to track security, LCM events, artifact changes,
and executed MaxL statements including imports of data or dimensions. The tracking
information is saved to a security audit log file or streamed to an external database.
You configure what events to track by defining an auditing policy file.