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:

  1. 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.

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

  3. The Monitoring apps require Windows authentication to be used on the virtual proxy it uses to connect. If this is not the default virtual proxy, replace \qrs\ with \<prefix>\qrs\ where <prefix> is the prefix of a virtual proxy with Windows authentication enabled.

    See: Default virtual proxy with prefix

Configuring multi-node environments

The configuration of multi-node environments differs depending on whether you use centralized logging or file logging.

Configuring when using centralized logging

Do the following:

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

  2. 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.

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

    See: Default virtual proxy with prefix

  4. 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.

  5. 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. See Logging.

Configuring when using file logging (centralized logging not enabled)

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

  2. 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.

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

    See: Default virtual proxy with prefix

  4. Share the Qlik Sense log folder (C:\ProgramData\Qlik\Sense\Log) on each RIM node.

  5. 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.

  6. 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.

  7. 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.

  8. 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 6 and 7.

    Do the following:

    1. Duplicate the Operations Monitor app in the QMC.

    2. Open the duplicate app in the Qlik Sense hub.

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

      Example: FOR each node in 'ServerLogFolder','RIM1','RIM2'.

    4. Save the app.

    5. Replace the existing Operations Monitor app by publishing the duplicate app to the Monitoring apps stream and selecting Replace existing app.

  9. Perform step 8 in the License Monitor.

Note: If you encounter problems when the central node is not a reload node, see: The Monitoring apps fail to reload in a multi-node environment .

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 following data connections need to be updated:

  • monitor_apps_REST_app
  • monitor_apps_REST_appobject
  • monitor_apps_REST_event
  • monitor_apps_REST_license_overview
  • monitor_apps_REST_license_login
  • monitor_apps_REST_task
  • monitor_apps_REST_user
  • monitor_apps_REST_license_user

Importing new Monitoring apps

The additional Monitoring apps: Log Monitor, Reloads Monitor, Sessions Monitor, Sense System Performance Analyzer, Sense Connector Logs Analyzer and App Metadata Analyzer are not by default available in the QMC. You need to import them to make them appear in the QMC.

Do the following:

  1. From the QMC start page, open Apps.

  2. Click P Import in the action bar.

  3. Click Choose File and navigate to %ProgramData%\Qlik\Sense\Repository\DefaultApps\

  4. Select the app to import and click Import.

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

  5. Repeat steps 2-4 for the remaining apps.

Note: The Sessions Monitor, Log Monitor, Reloads Monitor, Sense System Performance Analyzer, Sense Connector Logs Analyzer and App Metadata Analyzer apps are not automatically updated during a Qlik Sense upgrade. You must manually import them after an upgrade.

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.

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.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?