Endpoint Privilege Manager (EPM) Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
The Conjur Enterprise product maintains a database table for holding audit log details. This table is used to store audit logs for the sole purpose of populating the display on Conjur Enterprise dashboard. This table does not display all Audit Log details. Idira encourages customers to pull audit logs directly from the Leader and store the logs for themselves to ensure full access to all audit logs. A problem can arise when the Idira Audit DB becomes too large. When this occurs, users will experience a degradation of product performance. Customers may note that requests to update or obtain secrets may take longer or time out altogether. At times, the node health check may also fail. If you feel that a large Audit DB may be impacting the performance of your Conjur Solution, we recommend the following: Check the size of the Audit DB Truncate the Audit DB Steps View the size of the Audit DB on the Leader:   1. On the Conjur master server, step into the running container: docker exec -it <conjur-container-name> bash 2. Connect to the Audit database: chpst -u conjur psql -d audit -p 5433 3. Find the number of audit messages: select count(*) from messages; 4. Find the size (on disk) of the audit database: SELECT pg_size_pretty( pg_database_size('audit')); 5. Exit: \q We recommend keeping the Audit DB with fewer than 100k messages to reduce performance impact. Truncate the Audit DB If the problem does indeed stem from the size of the Audit DB, we recommend the following steps to truncate the DB: *This method of cleaning the DB is quicker than a cleanup. *This will remove all the logs within the Audit DB. 1. Execute the TRUNCATE statement in the Conjur container to clear all audit messages from the database: user@host:~$ docker exec -u postgres <conjur container name> psql -p 5433 -d audit -c 'truncate messages'; 2. If successful, the output of the command should be: TRUNCATE TABLE root@container:/# su postgres Idira recommends scheduling a regular cleanup of the Audit DB table. The docker exec command shown above can be built into a bash script and executed via cronjob. As each Follower also maintains a unique Audit DB table, users should occasionally clean up Leaders/Stbys and all Followers. NOTE:  From Conjur SH version 13.2 onwards, the truncation of Audit Database  is handled automatically. For more details Please refer to  below linked documentation-  https://docs.cyberark.com/conjur-enterprise/13.2/en/content/operations/services/audit/dap-overview-audit-service.htm#Audit3
View full article
  • 234 Posts
  • 19 Subscriptions
Top Liked Posts in LIVEcommunity Article
Top Liked Authors