Storage reduction for Atlas

Audit aging reduces the existing audit data in the Atlas system which is based on the end user criteria and configuration changes that users can manage. With this configuration, users can control the type of DDL events pertaining to schema changes that will be retained for a period of time determined by their compliance requirements.

Atlas creates audit events for creation, update, and deletion (CUD) of entities in CDP, including TAG/Classification and DML events. Notification processing with less significant metadata, exponential growth of audit events with no constraints, and retaining of audit data for long periods of time causes overhead on the application processing and consumes additional storage space, thereby causing operational inefficiencies.

Atlas supports various audit reduction strategies, pertaining to the type of audit data the users can store and the period of time that they can retain the data in the Atlas systems.

Some of the audit reduction options include:

  • DML Audit Filter - A hook based filter that skips processing of DML events.
  • Custom Audit Filters - Users can decide which audit events will be ignored..
  • Audit Aging - Users can purge existing audit data based on the criteria they set.

Note: Audit reduction is targeted only for the entity audit data which persists in the ATLAS_ENTITY_AUDIT_EVENTS table. Filtering and aging data is exclusive to Admin Audit data which typically persists in the atlas_janus table..