Command Line Flags

There are 3 modes the TelemetryDashboard.exe has, and one flag that can be added to any of these.

The three mode flags are:

-initialize

This will import the Telemetry Dashboard app into the environment as well as create all tasks and data connections to allow the metadata fetch to run and populate the application.

-fetchmetadata

This will generate the .csv files with all the metadata needed for the Telemetry Dashboard.

-test

This will simply test the connection to the Qlik Sense Repository Service to make sure the communication is working properly.

Additional Flags:

-uselocalengine

By default, the telemetry dashboard will use the central node engine for fetching engine objects to avoid load balancing rules. If this becomes an issue, this flag will use the engine local to where the metadata fetch is run.

-skipcopy

By default, the telemetry dashboard will copy itself to the share folder which is the location it needs to be in for it to function properly. Sometimes depending on the share, the UNC path is unable to resolve, and at that point you should use this flag. You will need to make sure the TelemetryDashboard.exe is indeed in the CORRECT location before triggering the task. The path it needs to be in will be in the logs, but it should be a folder called TelemetryDashboard. This folder should be at the root of the share folder for Qlik Sense. The account running the Qlik Sense Enterprise services should also have access to the executable.

-enginetimeout=30000

This is the time Telemetry Dashboard will wait for Qlik Sense Engine requests to complete. By default, the engine timeout value is 30000 ms. If you want to lengthen or shorten this value, this command line argument can be used. If you want this value to persist for every run, you will need to manually edit the first external program task.

-repositorytimeout=100000

This is the time Telemetry Dashboard will wait for Qlik Sense Repository requests to complete. By default, the repository timeout value is 100000 ms. If you want to lengthen or shorten this value, this command line argument can be used. If you want this value to persist for every run, you will need to manually edit the first external program task.

The last flag is -debug which can be added to any of these (enabled on -test by default) to enable debug logging.