We are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS! This application will enable you to answer questions like:
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?
The Entitlement Analyzer is only available for Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository for an overview of which monitoring app is compatible with which subscription type.
The Entitlement Analyzer app provides insights on:
Entitlement usage overview across the Tenant
Analyzer Capacity – Detailed usage data and a predication if you have enough
How users are using the system and if they have the right Entitlement assigned to them
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 are available via GitHub, linked below.
Anyissues, questions, and enhancement requestsshould be opened on theIssues pagewithin the app’s GitHub repository.
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 Platform Architects
Additional Resources:
Our other monitoring apps for Qlik Cloud can be found below.
@skozawa you should have 2 .qvd files that have the data of July since you run the app once back then. The recommendation is to have the app scheduled to run once a day and hence you keep building your history on those .qvd files (which you should also back up if possible). If you do not have those 2 .qvd files then it's most likely that they were either overwritten or deleted.
・The data of "2. /licenses/overview" is reset every month. If I leave the app being not reloaded more than a month, the data since I run the app for the first time in "2.qvd" will be overwritten or deleted on next reloading.
・If I reload the app every month (the recommendation is every day), the data since I run the app for the first time can be stored in "2.qvd".
2. That is correct yes. 3. "If I leave the app being not reloaded more than a month" -> if you miss a month and you do not update the overview qvd you will miss the quota for that month. if you reload and get the data for the next month then that month will be stored in the overview.qvd. Nothing should be overwritten or deleted in this scenario. The utmost recommendation is to run the entitlement analyzer app at least 1 time on a monthly basis. Daily or Monthly really depends on how you want to analyze the underlying data. I recommend daily since one can get a live view of the capacity minutes used, which is of significant value to monitor.
My qvd's for this app are overwritten by new app changes when I debug the app. I want to see historical data which was present earlier. Could you tell me how to refresh the app with all historical data?
Hello, In the latest version, for the initial load, not having any existing QVD files for that app, I had to force the incremental_qvds_available to 0 in Assignments' tab.
If incremental_qvds_available=0 then
Only then I could set it back to 1 for proper incremental load.
@kmn , when you mention you recommend to schedule the app to run once a day, do you mean a "scheduled reload" or actually opening the app in the browser once a day?