Configuring the Monitoring apps

All installations of Qlik Sense require some level of configuration of the Monitoring apps.

Configuring single node environments

Do the following:

Update the data connections ArchivedLogFolder by replacing C:\ProgramData\Qlik\Sense with the fully-qualified domain name (FQDN) path to the shared folder for Qlik Sense: \\<FQDN>\<QlikShare>\ArchivedLogs.

Update the monitor_apps_REST_ data connections by replacing localhost in the connection strings URL and trustedLocation parameters with the FQDN of the node where the repository resides.

If the virtual proxy uses a prefix, the monitor_apps_REST_ data connections must be updated to include the prefix used.

Note: Data in the Operations Monitor and License Monitor is not live, it is updated when the apps are reloaded. Reload frequency can be changed by editing the triggers for the task.

Configuring multi-node environments

Do the following:

Update the data connections ArchivedLogFolder by replacing C:\ProgramData\Qlik\Sense with the fully-qualified domain name (FQDN) path to the shared folder for Qlik Sense: \\<FQDN>\<QlikShare>\ArchivedLogs.

Update the data connections ServerLogFolder, by replacing C:\ProgramData\Qlik\Sense\Log with the FQDN path to the central node: \\<FQDN>\<UNC_Share>\Log.

Update the monitor_apps_REST_ data connections by replacing localhost in the connection strings URL and trustedLocation parameters with the FQDN of the node where the central Qlik Sense repository service is running.

If the virtual proxy uses a prefix, the monitor_apps_REST_ data connections must be updated to include the prefix used.

If you are using centralized logging, you need to update the QLogs data connection by replacing localhost in the connection string URL with the FQDN of the machine where the centralized logging database resides.

Note: The centralized logging database may or may not be enabled and may or may not be in the same PostgreSQL database as the Qlik Sense Repository Database.

Share the Qlik Sense log folder on all RIM nodes.

Add a new data connection to the Log folder for each rim node. This can be accomplished by opening an app, accessing the data load editor, and creating a new data connection. If you have five RIM nodes, you need to create five data connections.

For example, the data connection for RIM1 points to folder \\rim_node_1\<UNC_Share>\Log and is called RIM1.

Rename the new data connections in the QMC to remove the (username), which is appended to the data connection name. Example: RIM1 (user_183) is changed to RIM1.

Update the load script of the Operations Monitor in section logFolderList on line 5 by adding the names of all the new data connections created in step 7 and 8.

Do the following:

Duplicate the Operations Monitor app in the QMC.

Open the duplicate app in the Qlik Sense hub.

Edit the load script: Each new data connection name needs to be enclosed in single quotes (') and separated by a comma.

Default virtual proxy with prefix

For the Operations Monitor and License Monitor to reload correctly when the default virtual proxy uses a prefix, you need to manually add the prefix to the qrs data connections. The default URL is https://<FQDN>/qrs/app/full, where the FQDN refers to the node where the repository resides. If the virtual proxy prefix is "qlik", the URL needs to be as follows: https://<FQDN>/qlik/qrs/app/full.

The app is imported and can be published to the Monitoring apps stream.

Repeat steps 2-4 for the remaining apps.

Customizing the apps

It is possible to extend the Monitoring apps with visualizations you find useful in your particular environment. The Monitoring apps provide assets panels with the dimensions and measures they use. You can use those dimensions and measures to create customized visualizations on separate sheets that you can add to the apps.

The assets panels may also include extra visualizations that are not used on any of the apps’ sheets, but which can be useful in a particular environment.