Old auditing data taking up database space
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- Are there any alternative methods to manage audit data?
Resolution
-
As an alternative to saving all of the logging data into the database, instead, we may choose to save it to a JSON or CSV file. The same disk space requirements remain, but it can potentially make the data more manageable, especially when preparing for an upgrade. Configuration is outlined in our Configuring Audits documentation, see section: Reporting Audit Events in Liferay’s Logs and Console.
- To give Administrators greater control over audit data, this feature request - Ability to limit or clear existing audit logging has been raised to our Product Team for review.
Did this article resolve your issue ?