idea Re: extension usage dashboard/api, etc.. in Suggest an Idea

extension usage dashboard/api, etc..

simonaubert — Wed, 25 Nov 2020 15:12:24 GMT

As of today, there isn't a solution to get an idea of the extension usage. However, I think this is a crucial need, especially when upgrading QlikSense.

So, what I sugget :
-a standard usage extension dashboard
-the ability to query the data through API.

Best regards,

Simon

Re: extension usage dashboard/api, etc..

simonaubert — Fri, 03 May 2019 08:27:18 GMT

(I know there is dashboard available on Branch but it requires all the apps to be closed.. so we cannot use it on a huge Qlik sense install... where we mostly need it)

Re: extension usage dashboard/api, etc..

alec1982 — Tue, 09 Jul 2019 21:06:10 GMT

how do I do that?

Re: extension usage dashboard/api, etc..

bchastai — Tue, 10 Sep 2019 13:44:00 GMT

I agree completely. The new Qlik Visualization bundles are great, but they basically mean we have to either keep duplicate extensions (which slows down the system) or risk breaking hundreds of existing apps by removing the deprecated extensions. We *really* need an extension dependency checker!

Re: extension usage dashboard/api, etc..

dayashankar — Thu, 12 Sep 2019 04:36:48 GMT

Is there any update on extension details w.r.t app's as we are having 70+ third party extension hence we need details which all apps got impacted after upgrade of QLIKSENSE Application from Nov 2017 to June 2019.

Please share the details if you have it will really helpful as its very difficult to manually update details for each app's.

Regards,

Daya Jha

Re: extension usage dashboard/api, etc..

simonaubert — Sun, 26 Jan 2020 08:53:40 GMT

A little upgrade : we have now native container and in Qlik Sense February 2020 a new native navigation button. A good thing would be to remove all the extensions concerned in the Qlik Bundle with the correpsonding native object. However, when you don't know where you use extension, it becomes a painful task.

Re: extension usage dashboard/api, etc..

Levi_Turner — Thu, 19 Mar 2020 14:59:42 GMT

As an update, there is a tool which can provide this insight: https://github.com/eapowertools/qs-extension-usage-dashboard

It does require this project be setup: https://github.com/eapowertools/qs-telemetry-dashboard

Re: extension usage dashboard/api, etc..

simonaubert — Tue, 14 Apr 2020 09:12:48 GMT

@Levi_TurnerThanks, I will have a look

As an other turnaroud, we have this chrome extension that can display the extension used in the page

https://chrome.google.com/webstore/detail/add-sense/bbiljflfafkaejgdebbnmcohpidgkejj

Re: extension usage dashboard/api, etc..

Iqbal_Khan — Thu, 23 Apr 2020 14:19:32 GMT

@Levi_Turner Thanks,

Re: extension usage dashboard/api, etc..

Iqbal_Khan — Thu, 23 Apr 2020 14:24:55 GMT

@Levi_Turner

Thanks, I have installed Telemetry dashboard and Extension dashboard in my qliksense but extension dashboard is not giving correct count of extension. We have 142 extension but it show total installed extensions 85. can you please let me know the reason.

Re: extension usage dashboard/api, etc..

Levi_Turner — Thu, 23 Apr 2020 17:19:04 GMT

@Iqbal_Khan : Potentially due to the fact that the app does not parse / include:

Widgets
Mashups

Widgets are a challenge to parse but there is an improvement to add it. Mashups fundamentally aren't in apps so it makes no sense to include them.

Re: extension usage dashboard/api, etc..

Iqbal_Khan — Thu, 14 May 2020 15:28:16 GMT

@Levi_Turner : Thanks. I validated and found that only Extensions of type "Visualization" are extracted. Type "theme" and "mashups" are not pulled. Do you have any plan to include theme and mashups as well?

Re: extension usage dashboard/api, etc..

Levi_Turner — Thu, 14 May 2020 22:43:52 GMT

Theme is a fair ask, but would require a fair bit of work to fetch that metadata. Mashups will always be excluded. At their core, mashups are not inside an app. So the approach of mapping app <> extension does not make sense. It's a fair ask to see whether a mashup has been used but will not be in the scope of the Extension Usage Dashboard.

Re: extension usage dashboard/api, etc..

Iqbal_Khan — Fri, 15 May 2020 11:24:16 GMT

@Levi_Turner : Sure, If we can extract theme information that will be sufficient for our requirement. please help us once this is possible. Thank you very much.

Re: extension usage dashboard/api, etc..

Iqbal_Khan — Wed, 09 Sep 2020 09:56:02 GMT

@Levi_Turner : Extension usage dashboard is failing after QlikSense Upgrade from April 2019 to June 2020 Patch 1. When I run the app it failed while executing below query in "Sheet Owners from QRS" script tab. I noticed that '$(vLibConnect)' used in other script tab also but they executed successfully.

Not sure why it is failing in a particular tab "Sheet Owners from QRS" . I am pasting log file too at the bottom. Can you please help to fix this.

LIB CONNECT TO '$(vLibConnect)';

RestConnectorMasterTable:
SQL SELECT
"id" AS "id_u2",
//"objectType",
"engineObjectId",
"__KEY_root",
(SELECT
"id",
"userId",
"userDirectory",
"name",
"__FK_owner"
FROM "owner" FK "__FK_owner"),
(SELECT
"id" AS "id_u1",
"__KEY_app",
"__FK_app"
FROM "app" PK "__KEY_app" FK "__FK_app")
FROM JSON (wrap on) "root" PK "__KEY_root"
WITH CONNECTION(
URL "https://$(vCentralHostname)/qrs/app/object/full?filter=objectType eq 'sheet'",
QUERY "xrfkey" "abcdefg123456789",
HTTPHEADER "X-Qlik-Xrfkey" "abcdefg123456789"
);

Log file snippet:

20200909T093302.592+0000 0449 LIB CONNECT TO 'monitor_apps_REST_app_old'
20200909T093303.076+0000 Connected.
20200909T093303.077+0000 0451 RestConnectorMasterTable:
20200909T093303.077+0000 0452 SQL SELECT
20200909T093303.077+0000 0453 "id" AS "id_u2",
20200909T093303.077+0000 0454
20200909T093303.077+0000 0455 "engineObjectId",
20200909T093303.077+0000 0456 "__KEY_root",
20200909T093303.077+0000 0457 (SELECT
20200909T093303.077+0000 0458 "id",
20200909T093303.077+0000 0459 "userId",
20200909T093303.077+0000 0460 "userDirectory",
20200909T093303.077+0000 0461 "name",
20200909T093303.077+0000 0462 "__FK_owner"
20200909T093303.077+0000 0463 FROM "owner" FK "__FK_owner"),
20200909T093303.077+0000 0464 (SELECT
20200909T093303.077+0000 0465 "id" AS "id_u1",
20200909T093303.077+0000 0466 "__KEY_app",
20200909T093303.077+0000 0467 "__FK_app"
20200909T093303.077+0000 0468 FROM "app" PK "__KEY_app" FK "__FK_app")
20200909T093303.077+0000 0469 FROM JSON (wrap on) "root" PK "__KEY_root"
20200909T093303.077+0000 0470 WITH CONNECTION(
20200909T093303.077+0000 0471 URL "https://qlikprod.go.akamai-access.com/defproxy/qrs/app/object/full?filter=objectType eq 'sheet'",
20200909T093303.077+0000 0472 QUERY "xrfkey" "abcdefg123456789",
20200909T093303.077+0000 0473 HTTPHEADER "X-Qlik-Xrfkey" "abcdefg123456789"
20200909T093303.077+0000 0474 )
20200909T093304.133+0000 12 fields found: id, userId, userDirectory, name, __FK_owner, id_u1, __KEY_app, __FK_app, id_u2, engineObjectId, __KEY_root, __extra_,
20200909T093304.139+0000 Error: HTTP protocol error 400 (Bad Request):
20200909T093304.139+0000
20200909T093304.139+0000 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
20200909T093304.139+0000 <HTML><HEAD><TITLE>Bad Request</TITLE>
20200909T093304.139+0000 <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
20200909T093304.139+0000 <BODY><h2>Bad Request</h2>
20200909T093304.139+0000 <hr><p>HTTP Error 400. The request is badly formed.</p>
20200909T093304.139+0000 </BOD...
20200909T093304.139+0000 Execution Failed
20200909T093304.149+0000 Execution finished.

Re: extension usage dashboard/api, etc..

Levi_Turner — Thu, 10 Sep 2020 00:18:49 GMT

@Iqbal_Khan : Either upgrade to June 2020 Patch 5 for the bug fix for QB-1995 or see this variant of the app which works around things (https://github.com/eapowertools/qs-extension-usage-dashboard/issues/9).

Re: extension usage dashboard/api, etc..

simonaubert — Tue, 20 Oct 2020 07:50:11 GMT

Hello @Patric_Nordstrom @Levi_Turner

As mentioned here : https://github.com/eapowertools/qs-extension-usage-dashboard/issues/7

The extension usage dashboard shows even extension that has been deleted (but without mentioning it's deleted). In my opinion as previoulsy discussed, the root is the use of the Telemetry Dashboard. Extension usage must show only the current metadata while TS must show an historical data. Maybe using API instead of logs would solve that? I'm pretty sure it would take a couple of hours for a qlik dev to make a new monitor rest connection and plug it to the chart.

The sad part is that I have a project that needs to remove all illegitimate extensions and replace it with native object.

Best regards,

Simon

Re: extension usage dashboard/api, etc..

simonaubert — Thu, 29 Oct 2020 19:05:12 GMT

It has been updated today (I haven't tested it)
https://github.com/eapowertools/qs-extension-usage-dashboard/releases/tag/2.0.0

Re: extension usage dashboard/api, etc.. - Status changed to: Open - Not Planned

Jeffrey_Goldberg — Mon, 14 Jun 2021 18:10:24 GMT

However, I'm going to look into how to track it.

Re: extension usage dashboard/api, etc..

simonaubert — Mon, 14 Jun 2021 19:19:18 GMT

@Jeffrey_GoldbergThanks. I really hope for a native, out of the box solution.

Best regards,

Simon