We have enabled the audit design change in our Nolio production changing the parameter 'Audit Design Changes' in the menu Administration -> System Setting from false to true and restart the NAC Server.
We don't get any information in the Dashboard in the Audit History Report. Can you please assist what is the cause and resolution for same.
Release Automation 6.x
We verified and it is due to the fact that the Audit was earlier turned on and later switched off. With recent change in Audit to be enabled, the auditing service trying to process all the entries from auditing entry and taking time henceforth the delay. It will finish processing all entries and than the audit reports will be shown on the Audit History Report.
It can be verified reviewing the logs nolio_audit.log.* for any errors or to review audit entries getting processed
Log entries showing processing of historical data
2022-05-20T12:19:38.962+03:00 [auditThreadPoolTaskExecutor-1] INFO (com.nolio.platform.server.dataservices.services.audit.AuditServiceImpl:80) - Handling revision [1088465] from [Tue Oct 11 06:26:36 EEST 2016] by user [null]
2022-05-20T12:22:17.887+03:00 [auditThreadPoolTaskExecutor-1] INFO (com.nolio.platform.server.dataservices.services.audit.AuditServiceImpl:80) - Handling revision [6843050] from [Fri May 20 12:22:12 EEST 2022] by user [null]
Please let auditing service run for some day's and once it process all entries from auditing table it will be reflected in "Audit History Report"
Recommendation
It is important to carry out periodic maintenance of RA DB to make sure that the historical records no more required are purged periodically. It will help to keep a check on the DB size and hence will improve the performance of RA. Please refer CA Release Automation Database Care and Feeding for details around same.
General Consideration for purge
1: Retention days: The data policy to retain data of X+ days, so if X=3/6 month then schedule purge every 3/6 months
2: DB size: The policy to constraint or limit the DB size. Henceforth perform purge as required to shrink the DB size to retain it within permissible limits.