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.
Logs are monitored for errors so we can provide product stability, but, in general, you can read up on our data handling policy here: Product Privacy | Cloud
in the "Users" sheet, what is exacty the measure, duration of events ? is it the session time of a user, even if the engine is not used, that can explain why this duration is much longer than the consumption of capacities ?
@Sonja_Bauernfeind do you know if something happened recently in the backend that would wipe out all data prior to May 1, 2023? We haven't changed anything to the analyzer, but all historical info beyond the current month is gone.
Have customer using the Entitlement Analyzer app and he gets an "Error:All expresions are disable". The user is a tenant admin and the rest connection is working ok. Thanks!
Hello Team, Please your help, since at the time of downloading the detail of user logins by app in the Entitlement Analyzer, graph consumption listings is bringing me information of 2 to 3 minutes logins that I identified as unauthorized user login attempts to Apps. Is there any way to configure a filter to suppress this information, because as such it is not an access to the app, but a failed attempt. Thank you.
App consumption overview, appears to only have one month of data, and does not obey any of the other filters from other sheets where a past month might be selected
like
Time analysis assigned vs consumed where AssignedMonthText can be set, for example to April 2023
App consumption overview, still only shows the current month, for this example right now - MAY 2023.
How can we see past session related info in this SaaS/QCG app? like we used to be able to see in the Sessions Monitor and Operations Monitor, on Enterprise?
Hi. This app was working fine for me until my API key ran out last week. I created a new key, and replaced it in the connector, but it is still reporting as "401: Unauthorized". Nothing else has changed since it was last working, and I have the Tenant Admin role. Any suggestions?
Never mind. Had to tick the Encryption option, after putting the key in the connector.
In v1.2.11 to pull historical data you must go to the Variables section and change the variable Month_Start to the date you wish. Otherwise it will only pull data going back to the first time the app was run...Now(1). Suggest Qlik make this one of the items under Configuration instead.