Closed armandfrigo closed 2 weeks ago
Hey @armandfrigo , This looks like a feature request for the Entitlement Analyzer, however this is a request on the App Analyzer repo. The app analyzer pulls from 90 days back, while the entitlement analyzer pulls from the current month and forward due to it not propagating back the current license values. As far as stacking QVDs, we do not support this as the schema, field calculations, etc can change at any time between versions. We do of course have customers that attempt to stack them on their own, but again, we don't support this and it isn't currently planned. There have been however conversations around creating a secondary QVD version variable, so rather than stacking, if the schema between app versions remained constant, then the newer version could use the older QVD schema. This isn't planned, but the idea has been tossed around.
Hope this helps- Cheers,
Hello Daniel, thanks for your swift response, always a pleasure to read a comprehensive thread from you!
I am probably not the only one being confused considering the App Analyzer was enhanced to show platform usage (apps, sheets, ...), while the entitlement analyzer app got its "App Consumption Overview" sheet deprecated. In other words, I was on purpose adding this feature requests under the app analyzer because the platform usage analysis in scope have been transferred from the entitlement analyzer app to the App Analyzer (I cannot tell if that was an agreed choice or not, but it's a fact).
As you have mentioned, we are not the only client interested in looking at usage stats beyond the last monitoring app version upgrade. We are using such statistics to understand which users and apps have been successfully migrated (and used) from on-prem to Cloud, this is helping us to reduce the number of on-prem user license while monitoring we have enough with Qlik Cloud.
I understand there is no commitment from Qlik to ensure continuity with the schema or stats within the monitoring apps, yet I can confirm that such historical data (beyond 90 days) matters for customers who are still under the user licensing scheme.
As I have shared a QVF example, we also attempt to stack these QVDs on our own :-), to present the global picture to our management.
Have a great day! Armand
Hey @armandfrigo, Yes, deprecating the sheet in the Entitlement Analyzer and adding the data to the App Analyzer was a coordinated effort. This allows all Qlik Cloud customers to have access to that data without having to be on a Professional/Analyzer subscription type. I would like to emphasize that the change from pulling this data out of the Entitlement Analyzer and bringing it to the App Analyzer was a net positive regarding history duration, as we went from loading the current month in the Entitlement Analyzer to 90 days rolling in the App Analyzer. So it is a step in the right direction.
Thank you for the feedback. I will raise a conversation around QVD schema versioning support on our next steering call. It is possible that we may be able to implement it for just the App Analyzer, however it is typically in our best interests to apply these types of changes to all monitoring apps as they are standardized. This is of course a larger effort.
Cheers,
Thank you Daniel, much appreciated :-)
🚀 Feature
Load the incremental QVD files from previous application versions.
Motivation
Include usage statistics before the application was upgraded.
Additional context
Concatenate previous consumption QVD files: entitlement_analyzer_Consumption_2.2.1.qvd entitlement_analyzer_Consumption_2.3.0.qvd entitlement_analyzer_Consumption_2.4.0.qvd ...