Qlik Community

Qlik Monitoring & Administration

Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Highlighted
Employee
Employee

Sense App Metadata Analyzer

We are excited to share the official release version of the Sense "App Metadata Analyzer" app!

This is a "productized" version of the super app that @Daniel_Pilla and @LeviTurner posted on Qlik Branch (qs-app-metadata-analyzer).

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 aholistic 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:

http(s)://{server}/api/v1/apps/{GUID}/data/metadata
 
where {server} is your Qlik Sense Enterprise server and {GUID} is the application ID. Note that the application does not need to be lifted into RAM for the metadata to be accessed.

Data from this endpoint is derived as part of the app reload process, and therefore does not include any object or expression related metadata. The data from the endpoint includes:
* server metadata including number of server cores, total server RAM
* reload time
*app RAM base footprint
*field metadata including cardinality, tags, total count, RAM size
* table metadata including fields, rows, key fields, RAM size

 

Version History

  • v1.0.0 GA > First official release, compatible with June 2018 Sense and later, target release September 2019
  • Required Configuration: In the "configuration" section of load script, update the vu_central_node_host_name and vu_virtual_proxy_prefix variables as described in the load script.

 

Sheets:

sense_app_metadata_analyzer_dashboard.pngDashboard

 

sense_app_metadata_analyzer_app_availability.pngApp Availability

 

sense_app_metadata_analyzer_app_analysis.pngApp Analysis

 

sense_app_metadata_analyzer_threshold.pngThreshold analysis

Tags (1)
5 Replies
Partner
Partner

Re: Sense App Metadata Analyzer (BETA)

This seems great! I'll give it a try in the next weeks!
Partner
Partner

Re: Sense App Metadata Analyzer (BETA)

Great stuff. Thank you.

Kabir
Please do not forget to the mark the post if you find it useful or provides you the solutions 🙂
Partner
Partner

Re: Sense App Metadata Analyzer

Hi @Tyler_Waterfall ,

Is there a way to exclude the empty applications (the ones that have been just created or opened without  data)?
In those cases the endpoint returns nothing, and the reloads fails.

I wouldn't like to use a where clause with a fileSize >= (value) since even if empty, the application could have different sizes (i.e. if I upload an attached content)

Many thanks,
Riccardo

Employee
Employee

Re: Sense App Metadata Analyzer

Good question @rzenere . So you want to exclude apps which have no data (no rows) or no size on disk (fileSize) or?

What about apps used to generate QVDs which drop data at the end?

Partner
Partner

Re: Sense App Metadata Analyzer

Apps that generate QVDs... Depends. Sometimes we leave some statistics fields, so those have rows.
But definitely when the app has no rows/no size on the disk it would be nice to exclude it!

I thought again about the apps with attached files but have no rows, and those cases should already be excluded since the fileSize is the one of the app without attachments.
Unluckily I believe to have an issue with some application that have data and have been reloaded in September 2018, but I need to investigate more in order to understand why.


Taking a look at the response of the http(s)://{server}/api/v1/apps/{GUID}/data/metadata I see there are always (or most of the times?) three $$SysTable. Do you have any idea about what those are?

Riccardo