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.
Maybe this is useful for others user and the developer!
At one customer a get a problem when loading the script with variable: vMinutes
After searching why data was missing in the variable I found this. There is a variable incremental_qvds_available that is returning a 1 or 0. With this a check will be done if a QVD is existing. In my case it was returning 1 and results in missing data.
I put manually a 0 and load the script. No error anymore and put the 1 back in place. Now my dashboard is working.
I don't know why the variable was 1 in the begining. Maybe the Developer knows this instantly or it was a mistake from my side.
In Qlik Sense on Prem (Enterprise on Windows), you are able to track sheet usage using the governance app. However, in Qlik Cloud, no app like this currently exists.
I would recommend for you to log an idea for an app like this in our ideas section.
Can you help me with some info. I made all de necessary configurations, and the script has been running for more than 3 hours now. Do you know by any chance if all is in order.
@skozawa you can get older consumption data if you want. You will need to edit the script to do so. There is a reason for this behaviour of the app and I have explained it in one of my previous comments in this thread:
"So there is of course a reason why you cannot see historical data when running the app for the 1st time.
To explain this I would point my finger to the raw data that this app is using in order to produce the metrics: 1. /licenses/consumption API 2. /licenses/overview API
Number 1 has your history of how you are consuming your entitlements (licenses). For this data, the history is kept up to a point in the API and continued with the App in terms of QVDs.
Number 2 has your monthly quota, your overall units/minutes of your entitlement. This set of data is a snapshot and no history is kept within the API. The only way it can be built is via the app and incrementally storing the data into a QVD (on a monthly basis).
Now let's go back to your question. Many visualizations compare your consumption (present and past) against the quota you have (number 2). If you don't have historical values for your quota then your consumption cannot be compared correctly. Hence, your timeline starts the moment you run the app.
There is a solution though. If you know that your quota was the same in the past or you know the past quota values you can edit the script and "fake" historical tables for the Overview - do an inline and store them over the existing QVD.
Again, this is an example app that showcases the APIs behind it. You are free to make your own version"
I understand I need to edit the script and "fake" historical tables of my quota.
I assume that way is the case for that I want to load the data before the time when running the app for the 1st time.
If I want to load data from the time when running the app for the 1st time to present, do I need to "fake" historical tables of my quota,too?
For example, I want to do that:
July 1th : I runned Entitlement Analyzer for the 1st time. I could see data of July. August 1th : After reloading the app, I could see data of only August. I want to load data of both July and August.