This app iterates over every application metadata endpoint along with several other QRS calls (Nodes, Apps, Proxies, LB audit), ultimately providing a comprehensive dashboard to analyze your application metadata server-wide. This allows you to have a holistic view of the makeup of all of your Qlik applications, enabling you to have awareness at a granular level of the types of applications in your organization. This application is 100% native to Qlik without any installer, and is easy to configure within the Qlik Sense Enterprise environment as the app takes advantage of the existing 'monitor_apps_REST_app' connection to drive all of the REST calls.
As of the Qlik Sense June 2018 release, a new application level metadata endpoint is available. Data is populated for this endpoint per app post-reload in a June 2018+ environment. You can view this application metadata within your own June 2018+ environment at:
June 2020 Update: In version 2.2.1 and forward of the App Metadata Analyzer, a new Alerting sheet has been added, along with two new variables in the load script. The purpose of this sheet and added capability is to make integration with Qlik Alerting as simple as possible. This new capability and view allows for a Qlik administrator to easily see what applications have breached what thresholds (as well as how many) and be quickly alerted on them. It also allows for the administrator to disable alerts for specific applications and mark others as under review, which might have a different cadence. Please see the attached guide for much more detail and example policies/configurations.
v2.2.2 (July 2020) >
Replaced the "AppName" field with the "AppNameUnique" field in many visualization objects to properly visualize identically named apps.
v2.2.1 (June 2020) >
Resolved incremental load issue to include imported apps with metadata that had not yet been reloaded on the server
Resolved issue with application tag values not appearing
Resolved autonumber collision issue with "FieldNameUnique" and "TableNameUnique" fields, due to AutoNumber() being used pre and post QVD
Resolved issue where some threshold breaches were stored to QVD, forcing applications to be reloaded before a change of threshold would take effect
Removed system fields and system tables
Modified chart "Field # Records" to "Field Cardinality" on "Dashboard" sheet
Modified "Threshold Analysis" sheet to use boolean logic for measures over/under thresholds vs a dynamic range
Added in the sheet "Alerting" for visualizing threshold breaches and allowing for simple tie-ins to Qlik
Alerting and NPrinting
Added flagging of circular references
Added ability to ignore applications from "Alerting" page with specific tag value
Added threshold reference lines to "Dashboard" objects