Data Aging of Audit Trails and Account Sessions

Auditing is about accountability, and enables users to reconstruct and examine the sequence of events and/or changes in an event for an object. Although auditing is relatively inexpensive, you should limit the number of audited events as far as possible. Doing so minimizes the performance impact on the execution of audited statements and the size of the Event History.

 

To control the growth of the Event History, the Delete Objects effect now provides capabilities to define a "retention rule" for audit trails, that is deleting old / invaluable entries.