Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Qlik Sense - How to control the size of the Qlik Sense Logging Database when using Centralized Logging

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Bastien_Laugiero

Qlik Sense - How to control the size of the Qlik Sense Logging Database when using Centralized Logging

Last Update:

Jul 6, 2023 9:05:00 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 23, 2018 3:14:48 AM

Centralized logging has been deprecated with the Qlik Sense Enterprise on Windows May 2021 release. This article is only valid for previous versions. No support can be provided on Qlik Centralized logging as all Qlik Sense versions using it have reached end of life. 

The Qlik Sense Logging Database can grow very quickly depending how big your environment is. It might necessary to purge it to avoid performance issue and/or storage problem.

NOTE: Qlik Sense Centralized logging will be deprecated by the end of year 2021. See Deprecation of Centralized Logging in Qlik Sense Enterprise on Windows  

To do so

  • To set an archiving and purging schema you need to run the following in a Command Line:
    • "C:\Program Files\Qlik\Sense\Logging"\Qlik.Logging.Service.exe update --archive_age x --purge_age y (where archive_age value must be lower than purge_age, otherwise will fail)
      • Where X and Y are a days threshold
    To set a file size cap on the size of the database you need to run the following in a Command Line:
    • "C:\Program Files\Qlik\Sense\Logging"\Qlik.Logging.Service.exe update --maximum_db_size_in_gb n
      • Where n is the size in GB
    Note: This was written assuming a default installation path. You may need to adjust the path from "C:\Program Files\Qlik\Sense\Logging\" to your installation path.


Reference The logging database has grown too big

Labels (2)
Version history
Last update:
‎2023-07-06 09:05 AM
Updated by: