qlik-oss / qlik-cloud-entitlement-analyzer

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.

Important

This project is community supported. This means that you should not contact Qlik Support for help with these apps. See below for additional information on how to raise issues on this repository to ask for help.

Qlik Cloud Entitlement Analyzer

Note This application is one of a set of community built and supported monitoring apps for Qlik Cloud. For links to all monitoring apps, visit the Qlik Cloud Monitoring Apps repository.

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.

It provides information such as:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

Installing / Updating

These applications can be installed via an interactive Qlik Application Automation installer or manually using the PDF guide.

Subscription Compatibility

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

Support policy

This app is provided as-is and is not supported by Qlik. Over time, the APIs and metrics used by the app may change, so it is advised to monitor this repository for updates, and to update the app promptly when new versions are available.

If you have issues while using this app, support is provided on a best-efforts basis by contributors to this project.

If you have an issue:

• Review the FAQ section in this readme to see if your issue is a common one
• Review open and closed issues
• Open a new issue, following the issue template

If you are able to resolve the issue, then close your issue with the resolution, and if you feel inclined, open a PR with your proposed changes so that we can consider including the improvement in the next release of the app.

Thank you for your support!

qlik-cloud-entitlement-analyzer's Issues

Analyzer Capacity - Events duration vs Minutes used

🐛 Bug report

I'm trying to monitor users that use the Analyzer Capacity, and came across a difference between what is exposed between Events duration (which is calculated on durationMinutes) and Minutes used (which is calculated on minutesUsed).
After digging up a bit, I saw that the /api/v1/licenses/consumption endpoint (which is used by the Entitlement Analyzer) exposes directly this strange data.
Below an example for licenseUsage = TIME_LICENSE, where minutesUsed isn't always aligned with the durationMinutes

In the highlighted cells, I would expect a value <= of the minutesUsed (like the not highlighted cells).

For licenseUsage = ASSIGNED_LICENSE, minutesUsed is always 0, so durationMinutes is the only way for me to say how much lasted a session.
Am I reading those columns right in this situation? Or am I missing anything? (i.e. durationMinutes tracks also the time outside of an app?)

Steps to Reproduce

1. Configure the Entitlement Analyzer in an environment where the Analyzer Capacity 'license' is used
2. Check the data that is extracted by the Entitlement Analyzer; the check could be made:
   2.1. directly on the extracted qvd, or also
   2.2 on the Entitlement Analyzer app, checking the objects 'consumption listings' (sheet 'Users') and 'Capacity usage over time' (sheet 'Capacity usage over time')

Expected behavior

For users that are using Analyzer Capacity, minutesUsed should always be greater or equal to durationMinutes

Actual behavior

minutesUsed is lesser or equal to durationMinutes

Additional context

1. We noticed the issue with Entitlement Analyzer 2.2.1, but the same happens also on 2.3.0
2. From my interpretation, minutesUsed is the same value exposed on the Management Console and so, should be a multiple of the minimum 'block' of minutes that is used, while durationMinutes should be the actual session duration/time spent analyzing an application

Entitlement Analyzer is not showing historical consumption

Our tenant was launched let's say in January 2023 and since then entitlements are assigned and consumed by users. We would like to track those users who are not using their respective entitlements from, let's say, 6 months or X number of months/days. This is unavailable in the app. We are interested in two fields 1) Assignment Date and 2) UsageDate or Usage Month. We have started reloading and using this dashboard since November 2023, we expected that the "UsageDate" field holds values of the LastUsage date of all users since the launch of the tenant. However, we have handful of users who left organization months ago & other known users who are not using since 4 months, we don't have any values for them from the fields "UsageMonth" and "UsageDate".

UsageDate & UsageMonth holds data since Nov2023 only i.e. first reload of the app. However what about other previous months ? is our understanding wrong ?

Please find the attached screenshot.

The historical usage stats are changing after deleting users

We noticed that after deleting a user from a tenant, their usage stats seem to disappear from the app. This is impacting both recent usage and historical periods. Our expected behavior was that the historical usage should be retained in QVDs so that it is not impacted if any users are removed from the tenant, which will make them unavailable via API at the latest reload.

We have a weekly workflow that frees up licenses and deletes users based on certain period of inactivity. This is working as expected but also altering our historical usage stats showing in the app. I wonder if there is any option to retain the historical usage in the app after removing users from the tenant.

Loading historiccal data after upgrading to 2.3.0

I am running into an issue when trying to link my historical data to the output of the latest app. With userId deprecated in Assignments and replaced with subject in most places, what is the best way to connect the actual data with my historical tables populated by earlier versions of the app?

To give you an example, I want to load last X months of data stored in QVDs and show it in the latest app so we can still see the usage trends. Replacing userId with subject seems concerning as the same users would now have a different ID compared to their historical records. Would appreciate your help connecting the dots between historal and actual data in the app.

Error after migrating to 2.3.0

🐛 Bug report

We recently updated our Entitlement Analyzer monitoring app to 2.3.0 in a multi-tenant, parent-child environment and after doing so we receive an error when reloading the parent app. We see this error:

Storing Assignments-9.
The following error occurred:
Unexpected token: '-', expected one of: ',', ',', 'as', 'from', 'into'
The error occurred here:
Store Assignments>>>>>>-<<<<<<9 Into lib://Shared Monitoring Apps:Internal_Monitoring_Apps_S3/QlikMetaCollection/CompiledTenants/Monitoring/Entitlement Analyzer/Assignments-9.qvd
Data has not been loaded. Please correct the error and try loading again.

Steps to Reproduce

Updated all target/child tenants with Entitlement Analyzer 2.3.0 and also updated the source/parent tenant. All apps reloaded on schedule. When running source/parent tenant, receive the error mentioned.

Expected behavior

Expect the app to reload without errors.

Actual behavior

Error occurred and continues to occur.

Additional context

Prior Entitlement Analyzer version was 2.1.0

I understand that the monitoring apps might not be backward compatible, but I'm also not clear on how to clear out/ignore the old data so I can load the new versions data successfully.

Entitlement Analyzer should show a mapping of users in the tenant to entitlements & track duplicate assignments

🚀 Feature

The entitlement Analyzer should show a mapping of users in the tenant to entitlements and highlight those subjects which aren't present in the tenant.

It should also return the user subject as returned by the API so that customers can track where the subject but with different capitalization has resulted in multiple assignments.

Motivation

This supports tracking accidental/ lost/ duplicated assignments on the tenant which can't be viewed in the management console.

Entitlement Analyzer

🐛 Bug report

GPT
Aqui está a tradução para o inglês da lista fornecida:

🐛 Bug Report
(User utilization time is showing as zero)

Steps to Reproduce
(Data load)
(Open the visual)
(No data appeared)
Expected Behavior
(Display how much time was used by user on the dashboard)

Actual Behavior
(A clear and concise description of what actually happened.)

Additional Context

Track object exports

We'd like to be able to track object exports in a similar fashion as previously on-prem in Sessions monitor. This can help us to identify users who need extra enablement or support.

entitlement analyzer does not load historical data

Team,
I ask for your help since since 15 November we have seen failures in theMonitoring Apps (entitlement analyzer, reload analizer and app analyzer) application since it does not load historical data, we have reinstalled the application, we updated it to the latest version, we also created a new API key, but it still does not work. show historical information, it only shows the information for the days we have had in the month of December and we need to see the information for the month of November 2023, we appreciate your collaboration by telling us what we should configure or what we can do to solve it.

Thank you very much, we appreciate your prompt attention.

Entitlement analyzer failing on the schedule after 1st setup

🐛 Bug report

(A clear and concise description of what the bug is.)

Steps to Reproduce

1. setup entitlement analyzer
2. setup connection with timeout of 10000
3. Run the schedule
4. Schedule is failing.

Expected behavior

Get an output on Entitlement Analyzer

Actual behavior

We have setup entitlement analyzer in our environment for 1st time and it is hitting 3 hours of the timeout and failing. The maximum time out that we can set it 10000.

I have also user optional configuration to get data only for 1 day with variable SET vu_initial_days_back = 1;

RestConnectorMasterTable << RestConnectorMasterTable
failed to complete reload: Failure: Request aborted (15 GENERIC ABORTED)
The following error occurred:
User abort (Reload canceled due to exceeding maximum duration)

Additional context

(Add any other context, link to demo or screenshots about the issue.)

Allow use of Entitlement Analyzer app for capacity licence in Qlik Cloud

Hi,
We have installed the new Entitlement Analyzer v2.3.0 and set up and configured it.
We are on capacity licencing.

Post reload in summary it shows:

---

WARNING! This tenant is on a capacity-based license, which the Entitlement Analyzer does not support as it analyzes user-based licenses. Dropping all tables and halting...

---

Nowhere mentions this in the guidance or troubleshooting. <<< needs updating.

Regardless of the capacity licences being different, this app still provides some useful user and app use data for us.

Please can the guidance/troubleshooting be updated, and also the app script be reviewed to allow to be used in a capacity licencing tenant?

Regards, Carl.

Disabled users not visible for consumption {v2.3.0}

🐛 Bug report

For users that have consumed analyzer capacity minutes, but are then disabled, the user information disappears from the Entitlement Analyzer. There are minutes consumed, with a NULL value for the user information.

Steps to Reproduce

1. Have an analyzer capacity user that has consumed minutes.
2. Disable the user
3. Reload the Entitlement Analyzer
4. See the user info has disappeared

Expected behavior

For usage in the past, even if the user is disabled, I would like to see what user has consumed the minutes.

Actual behavior

The consumed minutes are shown without user info

Update Entitlement Analyzer app with the last 12 months of usage consumption stats

🚀 Feature

At my employer, we just started using the Entitlement Analyzer app and noticed the usage consumption records are filtered to the current month only. For audit purposes, we'd really like to be able to track the last 12 months.

As a Qlik admin and developer, I made an attempt to update the code to no avail.

Would it be possible to have this enhancement available?

Analyze sheet usage, similar to what was available in on-prem Qlik

Add data about sheet usage

In on-prem Operations monitor app, there was an sheet tracking usage of app sheets, which enabled us to implement life-cycle management app or Qlik environments and make regular cleanups of unused sheets.

Motivation

Currently we are not able to identify which sheets are used and which are not. This means we cannot clean unused sheets and we must rely on users to clean their own sheets regularly. But this also applies to public sheets. There's no point of maintaining sheets which are not used. Or perhaps we need to work on user enablement.

Looking at the API documentation it seems this is not possible with data the API provides right now. Is somethings like this on the roadmap?

Spelling error in 2.3.0

🐛 Bug report

Spelling error in v2.3.0 (reported by Lucke, thank you)

Credentials are not reflected correctly after changing them

🐛 Bug report

Hi.
Deploy the EntitlementAnalyzer app in your tenant to see how your users are using it.
Among them, there is a problem that when the user's credentials are changed (from AnalyzerCapacity to professional), the changed credentials are not reflected.
*Not reflected for some users.

Steps to Reproduce

1. change someone's entitlement.
2. Check the entitlementAnalyzer(Do Reload)

Expected behavior

I expect any of the following to change.
1 Entitlement_Assigned
2 Consumed Entitlement
3 Current entitlement
4 Entitlement
5 Entitlement_Consumed

Actual behavior

None of them will change

Additional context

[Question 1]
If you know why this happens and how to make it happen, please let me know.

[Question 2]
The items referred to as credentials are:
I would like to know the difference between them.
1 Entitlement_Assigned
2 Consumed Entitlement
3 Current entitlement
4 Entitlement
5 Entitlement_Consumed

Credentials are not correctly reflected for
usersFor 2 and 5, analyzer_time information is included, but professional information is not reflected, and all 5 items above are displayed as [-].

Question 3:
If you look at the audience data according to the data model,
the 1:Entitlement_Assigned table exists with a TenantUserKey of 1, but all other items are
[-]2:TenantMetadata There is no record associated with the target user in the table Entitlement_Assigned and the
TenantID of the target user in the table is [-], so it is not linked to TenantMetadata.
I understand that, but does this mean that the data is an outlier?

Entitlement analyzer error

Hello ,
I have a problem with The Entitlement analyzer app , it has not load historical data , i have only data for current month , also the calendar has only data for this month !
All other months data is null