Home > Tooling appendix > Monitoring Apps Deployer

Qlik Cloud Monitoring Apps Deployer

Type: Qlik Automate template

Support model: Installer automation supported by Qlik Support. Apps it installs are community-supported (with the exception of the Data Capacity Reporting App, which is fully Qlik-supported).

Subscription model: All

Roles: Tenant Admin (TA)

Last verified: 2026-05

Benefits:

• Set-and-forget install and upgrade for the community monitoring apps
• Automated API key rotation for the data connection
• Automatic detection of installed app versions via tags

Goal

First-time orientation. Qlik Automate is the no-code automation runtime included in every Qlik Cloud tenant—open it from the activity-center switcher in the top-left of the hub (the end-user landing page at https://<tenant>.<region>.qlikcloud.com, distinct from the admin console at …/console). A template in Qlik Automate is a prebuilt automation you import into the tenant, configure with your own variables, and run on demand or on a schedule.

A set-and-forget install of the community-maintained monitoring apps is provided by the Qlik Cloud Monitoring Apps Deployer template in Qlik Automate. As of the December 4, 2025 update, the unified deployer replaces the original separate installer / API-key rotator templates; per the workflow guide, disable or delete any existing installers, and create a new automation. Source: Qlik Cloud Monitoring Apps Workflow Guide.

The Qlik Cloud Monitoring Apps project is community-supported. Qlik doesn't support these apps with the exception of the Data Capacity Reporting App.

What the deployer does

• Installs / upgrades all or a subset of monitoring apps from Qlik's qlik-cloud-monitoring-apps OSS repository (Access Evaluator, Answers Analyzer, App Analyzer, Automation Analyzer, Entitlement Analyzer, Reload Analyzer, Report Analyzer). The Console Settings Collector isn't a deployer target—it ships alongside the OEM Dashboard releases.
• Creates required spaces (shared / managed) and the analytics REST connection.
• Creates / rotates the API key for the data connection.
• Creates a daily reload schedule and (optionally) reloads apps after install.
• Tags installed apps with QCMA - {appName} and QCMA - {version} so subsequent runs detect them; manually installed apps are not detected and will be installed side-by-side.
• Supports both user-based and capacity-based subscriptions (subject to per-app compatibility—see the applications matrix in the OSS repo).

Configuration variables

Set these variables before the first run:

• configuredMonitoringApps
• refreshConnectorCredentials
• reloadNow
• reloadScheduleHour
• sharedSpaceName
• managedSpaceName
• versionsToKeep

Recommended cadence

Tasks

Gotchas

• The deployer only manages apps that bear the QCMA - {appName} and QCMA - {version} tags. Any monitoring apps installed manually before the deployer was first run won't be detected; the deployer will install fresh side-by-side copies. Plan to retire the manually-installed copies after migration.

Roles for running and consuming

References

• Qlik Cloud Monitoring Apps Workflow Guide
• qlik-cloud-monitoring-apps (OSS repo)
• The Qlik Sense Monitoring Applications for Cloud and On Premise
• All templates (Qlik Help)

Tags: #monthly #tooling #monitoring_apps #deployer #qlik_automate