Qlik Cloud Monitoring Apps - App Analyzer Update - Session Level Data

[Michael_Tarallo]

In august 2020 we introduced the App Analyzer for Qlik Cloud tenants, a powerful monitoring tool which tracks metrics such as an app’s memory usage, ensuring you stay within your quotas. It also aids in app optimization by revealing field and table sizes, and highlighting potential data modeling issues like synthetic keys and data islands.

[Michael_Tarallo]

The latest update to the App Analyzer brings a new feature: session-level data. Now, the App Analyzer can answer vital questions, such as which users are accessing which applications, how long they stay in each app, what sheets they use, the duration on each sheet, and the frequency of navigation between sheets. It also tracks the number of concurrent users within an app or across all apps in the tenant. The App Analyzer is released and updated by Master Principal Analytics Architect @Daniel_Pilla. He will monitor this thread should you have any questions. 

In summary the App Analyzer’s key benefits include maintaining app size quotas, tracking user adoption, optimizing data models, and now analyzing user and session-level behavior.

The app analyzer can be easily programmatically installed along with all of the other monitoring apps via an out of the box Qlik Application Automation template. Please visit the links below for more information and to get started using it. 

Resources: 

• The Qlik Sense Monitoring Applications for Cloud and On Premise
• Qlik Cloud Monitoring Apps Workflow Guide
• Original App Analyzer / Qlik Cloud Monitoring Apps Demo

[robert99]

Hi Daniel

I can see the sheet_id. But is there any easy way to obtain the sheet Name in the table (as opposed to a link to the sheet)

Thanks

[AlexOmetis]

@robert99 - I looked into this and, at the moment, the Sheet Name is only accessible through Engine APIs (which potentially requires a session and web sockets etc), not the REST APIs that the monitoring apps use. 

The way I worked around it was to run a Qlik-CLI script to run through all apps, exporting a list of the Sheet IDs and names to CSV... then imported this to an app that could link to the rest of the data on Sheet ID.

Here's the (somewhat untested) PowerShell I used... it takes a long time (hours) to run on a big environment. Apparently it's possible to pararellise in PS but that's beyond my skills!

.\qlik context use $Context

$apps = .\qlik app ls --json --limit 10000 | ConvertFrom-Json

$apps | Export-Csv data\$Context-apps.csv -NoTypeInformation

$sheetList= @()

foreach ($app in $apps)
{

	Write-Host APP: $app.name

	$sheets = .\qlik app object ls --no-data --json --app $app.id  | ConvertFrom-Json | Where-Object {$_.qType -eq 'sheet'}

	foreach ($sheet in $sheets)
	{
		Write-Host SHEET: $sheet.title $sheet.qId
		$sheetList += [PSCustomObject]@{
			appId		= $app.id
			sheetId		= $sheet.qId
			sheetTitle 	= $sheet.title
		}
	}

	# Inside the loop so we can see the file building as we go
	$sheetList | Export-Csv data\$Context-sheets.csv -NoTypeInformation

}

[Daniel_Pilla]

Hi @robert99 ,

As @AlexOmetis states above, you unfortunately can only fetch this data from the Engine API at this point in time, which requires something like the Qlik-CLI (which importantly can open apps without data for this information) to scan a tenant.

This metadata is on our roadmap to surface via REST as part of a larger initiative, but I do not have a timeline for when that will become available. When it does, rest assured (pun intended) that it will be included in the app ASAP.

Cheers,

[robert99]

 @Daniel  @AlexOmetis 

Thanks for the replies. I will give this a go as manually doing this using the sheet link is a bit boring (I was about 30% through and hoped there was an easier way).

But now it partly entered in the much improved App Analyser (using an Excel load and apply map) I think the sheet information is almost essential. I will get it all set up and report back. As to what the most popular sheet layouts are.

Thanks Robert

BTW. Qlik will not let me enter Daniel_P*lla. 

The message body contains P*ll, which is not permitted in this community. Please remove this content before sending your post.