Skip to main content

Support Updates

The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics.

Skip the ticket, Chat with Qlik Support instead for instant assistance.
Community Manager
Community Manager

Hello Qlik Users! 

How can I track the usage of my Tenant over time? How are my entitled users using the Tenant? 

How can I better understand the usage of Analyzer Capacity vs. Analyzer & Professional Entitlements? 

These are a couple of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS! 

Entitlement Analyzer.pngThe Entitlement Analyzer will help answer those questions and more! The app provides insights on: 

  • Entitlement usage overview across the Tenant 
  • Analyzer Capacity – Detailed usage data and a predication if you have enough 
  • Understand how users are using the system and if they have the right Entitlement assigned to them 
  • Understand which Apps are used the most by using the NEW "App consumption overview" sheet
  • And much more! 




The Entitlement Analyzer uses a new API Endpoint to fetch all the required data and will store the history in QVD files to enable even better Analytics over time. 

 A few things to note: 

  • This app is provided as-is and is not supported by Qlik Support. 
  • It is recommended to always use the latest app. 
  • Information is not collected by Qlik when using this app. 


The app as well as the configuration guide can be found at the bottom of this post. This app was created internally and will be supported by the developers of the app. They will be following this thread so be sure to post any questions or issues here so they can be addressed. 

Be sure to subscribe to the Qlik Support Updates Blog by clicking the green Subscribe button to stay up-to-date with the latest Qlik Support announcements. Please give this post a like if you found it helpful! 

Kind regards, 

Qlik Digital Support Team 



Change log:

Oct. 7, 2021: Updated and attached latest QVF file for Entitlement Analyzer. The new version contains details about open events and therefore allows customers to better understand their consumption of the tenant. 

Oct. 20, 2022: Updates to legacy version and new app with OEM features available.



Customer Type

Ongoing Development

Entitlement Analyzer – Current.qvf

If this is the first time installing this application, use this application. This version addresses bug fixes and introduces support for multitenancy. If “upgrading” to this version from an older version of the Entitlement Analyzer, historical data will be lost.

Direct, OEM

Yes – all new bug fixes and features will be addressed in this version and forward.

Entitlement Analyzer – Legacy.qvf

This version addresses bug fixes and is intended to be used by existing Direct customers to upgrade from the old version while keeping their existing history.


No – this version of the app will be the last version for Direct customers only.



Digital Support
Digital Support

@chaas So glad to hear!

All the best,

Partner - Contributor III
Partner - Contributor III


has there been a change to the data reported by the licenses/consumption endpoint? around Tuesday last week?

We have noticed a huge spike in Sessions being reported. One user has gone from using about 200 sessions per month to 2.5k in March alone.

On investigation this user has API keys associated with it for a number of different purposes including Qlik Data Transfer.

Looking into the measures in the Entitlement Analyzer App I can see that the "id" field from the Entitlement_Consumption table is used in the Sessions Measures and not the "sessionId" field.

A large number of these rows have a sessionId of '', when I filter them out the sessions measures for this User appear to correlate with previous trends.


Hi @Alastair_Ometis 
The correct expression to count sessions related to entitlement consumption is what is currently used in the app (master measures) and that is count(id). sessionId is an engine-related session that can be empty in some cases and therefore we do not use that to count entitlement-related sessions/events. I hope that covers your question.


Luminary Alumni
Luminary Alumni

Is there a way to only view users who currently have a licence applied?  It shows me usage for users who've had their licence removed and makes it hard to look at which users are not currently utilising their licence.  

Partner - Specialist
Partner - Specialist

@kmn - thanks for the clarification of "entitlement  consumption session" and "engine session". Are you able to answer the first question @Alastair_Ometis asked about the endpoint that counts the sessions? As he said, we've seen sessions for a single user that is used by Qlik DataTransfer go up by well over 10x. It seems to mostly affect Qlik DataTransfer but we have seen an increase generally out of line with any potential growth in actual usage... 


@AlexOmetis  those sessions are most likely engine sessions and are getting triggered via the user that runs Qlik Data Transfer. Qlik Data Transfer is essentially calling the spaces, temporary-contents, and qix-datafiles endpoints non-stop while it's uploading flat-files and QVDs. So that could be a very good explanation of why you are seeing that increase.

Partner - Specialist
Partner - Specialist

@kmn I'm sorry to keep pressing the issue, but are you confirming that the logging of those sessions is a new thing that was released a few weeks ago? QDT has been running for this customer for over 2 years and this is the first time they're seeing thousands of sessions a day and they're understandably wanting to know why. There's nothing in the release notes (here, here or here) that I can see about a change in logging detail/approach. 

If that is the case, it's probably a good thing - more logging is generally helpful. However if that's not the case, then we may need to look deeper into this as it could indicate a system or security issue.


@AlexOmetis I said it could be / that's what strikes me as the most reasonable explanation. That being said, I will need to examine this more thoroughly to give you a more confident response.

Partner - Creator III
Partner - Creator III

Exact Version of the Qlik Data Transfer?


Do you collect logs to improve the application?