Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

QlikWorld 2023, a live, in-person thrill ride. Save $300 before February 6: REGISTER NOW!

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs

Showing results for 
Search instead for 
Did you mean: 

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs


It is finally here: The first public iteration of the Log Analysis app. Built with love by Customer First and Support.


"With great power comes great responsibility." 


Before you get started, a few notes from the author(s):

  • It is a work in progress. Since it is primarily used by Support Engineers and other technical staff, usability is not the first priority. Don't judge. 
  • It is not a Monitoring app. It will scan through every single log file that matches the script criteria and this may be very intensive in a production scenario. The process may also take several hours, depending on how much historical data you load in. Make sure you have enough RAM 🙂
  • Not optimised, still very powerful. Feel free to make it faster for your usecase. 
  • Do not trust chart labels; look at the math/expression if unsure. Most of the chart titles make sense, but some of them won't. This will improve in the future. 
  • MOD IT! If it doesn't do something you need, build it, then tell us about it! We can add it in. 
  • Send us your feedback/scenarios!



Qlik Sense Enterprise on Windows (all modern versions post-Nov 2019)



How to use the app:

  1. Go to the QMC and download a LogCollector archive or grab one with the LogCollector tool
  2. Unzip the archive in a location visible to your user profile
  3. Download the attached QVF file
  4. Import/open it in Qlik Sense 
  5. Go to "Data Load Editor" and edit the existing "Logs" folder connection, and point to the extracted Log Collector archive path
    1. If you are using a Qlik Sense server, remember to change the Data Connection name back to default "Logs". Editing via Hub will add your username to the data connection when saved.
  6. Go to the "Initialize" script section and configure:
    1. Your desired date range or days to load
    2. Whether you want the data stored in a QVD
    3. Which Service logs to load (Repository, Engine, Proxy and Scheduler services are built-in right now, adding other Qlik Sense Enterprise services may cause data load errors).
  7. LOAD the data!


My workflow:

  1. I'm looking for a specific point in time where a problem was registered
  2. I use the time-based bar charts to find problem areas, get a general sense of workload over time
  3. I use the same time-based charts to narrow in on the problem timestamp
  4. Use the different dimensions to zoom in and out of time periods, down to a per-call granularity
  5. Log Details sheets to inspect activity between services and filter until the failure/error is captured
  6. Create and customise new charts to reveal interesting data points 
  7. Bookmarks for everything!


Notable Sheets & requirements:

  • Anything "Thread"-related for analysing Repository Service API call performance, which touches all aspects of the user and governance experience
    • Requirement: Repository Trace Performance logs in DEBUG level. Otherwise, some objects may be empty or broken.
  • Commands: great for visualizing Repository operations and trends between objects, users, and requests
  • Transactions: Repository Service API call performance analysis. 
    • Requirement: Repository Trace Performance logs in DEBUG level. Otherwise, some objects may be empty or broken.
  • Task Transactions: very powerful task scheduling analysis with time-based filters for exclusion. 
  • Log Details sheets: excellent filtering and searching through massive amounts of logs.
  • Repo + Engine data: resource consumption and Thread charts for Repository and Engine services, great for correlating workloads.  

*It is best used in an isolated environment or via Qlik Sense Desktop. It can be very RAM and CPU intensive.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.


Related Content 

Optimizing Performance for Qlik Sense Enterprise - Qlik Community - 1858594

Specialist III
Specialist III

@Mario_Petre , thanks for this, very clear and usefull

Version history
Last update:
‎2022-09-09 04:09 AM
Updated by: