My audit logs are taking a substantial time to load, why could this be?
If you are on a version previous
, we significantly enhanced the performance on the audit log pages by using database specific pagination SQL to handle large tables. This enhancement was applied to the Trigger Logs, Completed Jobs, Job File Audit, AS2, FTP, FTPS, GoFast, HTTPS, and SFTP audit log pages.
Upgrading to version 5.7.0 or higher should enhance your Audit Log loading speed.
If you are on a version higher than 5.7.0:
Check your database statistics to see if you have one or more tables that are extremely large. If you have only one page of your audit logs that are not loading, you may have a table that is getting too large to handle properly. (System -> Database Configuration -> Statistics)
To fix this issue, there are two recommendation in which you can adjust your setting to lower the size of your table.
- Lower the days to keep your Audit Logs. This can be found by going to Logs/Reporting -> Log Settings (Services or Job Logs) and lowering the days to keep logs.
NOTE: Lowering the retention days by a large number can cause significant overhead on the database. If your database table is in the millions, it is highly recommended to reduce the number of days in small step pattern. (Ex: reduce by 5 days - restart - allow it to purge - reduce another 5 days - restart - etc)
- Exempt events you may deem unnecessary. For example, you can exempt successful connections for one or more IP Addresses.