This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--HxUlBB9m1VEcJj0dO9sBDwd2v86tIQdk5
Content-Type: multipart/mixed; boundary="HjK7R6pAQfhTK2JA4pVCDr6ifqD6oPb94"
From: Sven Kieske <svenkieske(a)gmail.com>
To: users(a)ovirt.org
Message-ID: <571F7625.9010906(a)gmail.com>
Subject: Re: [ovirt-users] audit_log table performance tuning
References: <640699674.62984134.1460671956028.JavaMail.zimbra(a)redhat.com>
In-Reply-To: <640699674.62984134.1460671956028.JavaMail.zimbra(a)redhat.com>
--HjK7R6pAQfhTK2JA4pVCDr6ifqD6oPb94
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 15.04.2016 00:12, Marina Kalinin wrote:
Hi,
=20
Any suggestions or maybe already available features in the pipeline for=
tuning
the database, and specifically the audit_log table?=20
=20
The problem today is that with multiple applications accessing the engi=
ne through
the RestAPI, especially deployments with CloudForms, create hu=
ge 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 da=
tabase and results in a terrible performance of engine and inaccessible W=
eb UI.
=20
The solution today is to delete those records from the table [1]:
=3D> delete from audit_log where message like '%logged%';
=20
=20
Are there any current tunings we can apply to the database?=20
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
exac=
t issue.
=20
=20
Hi,
I remember filing a BZ about this topic some years ago.
I will mail it tomorrow to this thread as I had this exact issue, as a
user of the rest api (without any persistent authentication).
the answer, as I recall (I haven't access to this BZ atm), was to simply
truncate the event log, which is far from a "solution" at all.
kind regards
Sven
--HjK7R6pAQfhTK2JA4pVCDr6ifqD6oPb94--
--HxUlBB9m1VEcJj0dO9sBDwd2v86tIQdk5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCAAGBQJXH3YlAAoJEAq0kGAWDrqlCDkL/1aXdxwchuwNzcdILTZrVxII
w5LjTf++y307UmjM+31u+kZ1jdSiSDr5Xi/9FtKxDixJoQEDkUMTUXv8vPd+CxgW
3xtahcAaQPTOPu3U1yoDTVmyBDx5bi9T6QhMYqVhfiXQfyxJbMEC5iUZAlR4kNF4
Rcg99jaQlfPiQS+L7hUdSjL3gGzNQ9GLRTDiVDVBMFgtyWB3RQp1wU9rfe1OHXtw
zwM23A8qVAQegmiGYBp2uz5D0AxwFdnUjz/IVs6rOP8rHpRSN3hUaDVCIEyOtkHW
19bvDQQoIPBhhrmlVojxTvFuV+UrRXb0jZ7xDD445niCg2MSJv7shtj8wB12Hg1i
LnkRYti8XRnV/V4SZMiBjYMpnexdM6BD6wdwaeeWwu1iQVlekWD4eHiZGAViPD+k
O+/O1JxrvP9Mho3vuuXmmWbGl6eHh8x9WQGXOFLtZsy8XY+bhT2lfMJXjDKd51te
AlmhHIkwE3Dfkp70SKTXJu6Mtgsh6TVCGF6q6GoVfw==
=sSZH
-----END PGP SIGNATURE-----
--HxUlBB9m1VEcJj0dO9sBDwd2v86tIQdk5--