Hello
I reopen one topic again because I still have the same problem where the tables audit_trail_events and page_saves are too big. We are running version 3.148.0-stable on prem. I will like to know if in more recent version this problem doesnt happen?
schema_name | table_name | total_size
-------------+--------------------+------------
public | audit_trail_events | 7180 MB
public | page_saves | 27 GB
Hi @Jorge !
Sorry to hear that you are still dealing with this issue. Unfortunately, there is no built-in retention setting for the data, so you have to prune/manage your data manually.
audit_trail_events can generally be deleted safely since it is just historical logging of user actions.page_saves : you can join on the tags/releases table so you don't delete saves tied to a release you might need to roll back to.LOG_AUDIT_EVENTS/HEC) and then deleting the local table.The most recent on-prem version does not address this retention functionality at the moment, but I will add your request to our internal feature request to consider for the future!
In the meantime, were you able to try the recommendations in your previous thread here?
-Jen