Any suggestions or maybe already available features in the pipeline for tuning 
the database, and specifically the audit_log table? 

The problem today is that with multiple applications accessing the engine 
through the RestAPI, especially deployments with CloudForms, create huge amount 
of login records in the audit_table. Which, in turns, consumes most of the 
available memory on the machine running the engine and the database and results 
in a terrible performance of engine and inaccessible Web UI.

The solution today is to delete those records from the table [1]:
=> delete from audit_log where message like '%logged%';

Are there any current tunings we can apply to the database? 
And if not - do we have any RFEs on limiting the records entered to the 
database or a way to delete/filter those records somehow from the WebUI?
All I could find was RFE#1120659 [2], but it does not describe the exact issue.


[1] https://access.redhat.com/solutions/2110011
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1120659
Users mailing list

Reply via email to