Clarity LOG_DETAILS table is large / filling up

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

DBA noticed that LOG_DETAILS is large and filling up and takes a lot of space on disk and counts not being reduced down. What are the best practices? 

Environment

All Supported Clarity Releases

Resolution

Best Practices

• Table LOG_DETAILS is being populated by Tomcat access log import/analyze job
  • This job runs daily (by default) and adds session information in the database for review
  • You are then able to review the information on Clarity usage and sessions in Log Analysis page in Clarity - Home - Log Analysis in Classic
  • The portlets there give you the information on application usage and can go back as much as you have information in the LOG_ tables
• To keep the records in the table under control and make sure you do not keep any old records, you have to regularly run the job Delete Log Analysis Data to remove any old records
  • We recommend scheduling this job weekly off work hours
  • Set the log retention accordingly to what your company is needing for review

Addressing a large number of records in LOG_DETAILS

• If you have a significant amount of records built up in LOG_DETAILS already and have not been running the job, we recommend to run a few jobs with different date parameters to gradually remove the data and not run just 1 job for all the data
  • We recommend batching the removal to make sure it does not affect the application performance
  • You may try the test dates on your lower environments to gauge the amount of time this is going to take