Content

• Chapters
• Environment overview
• Zabbix Server set-up
• Clone the Zabbix docker repository
• Setting up environment variables
• Re-link compose.yaml to our preferred compose file
• Logging in for the first time
• Zabbix Agent installation on Windows Server
• Zabbix Server Configuration
• Adding the first Server
• Importing Qlik Sense Enterprise for Windows templates
• Linking templates to hosts
• Engine Healthcheck Monitoring with HTTP Agent example
• Steps to configure a new HTTP Agent for QSE Health monitoring
• Defining the Virtual Proxy prefix for Zabbix HTTP Agent
• Resources & Links

Chapters

• 01:33 - Why use Zabbix
• 02:35 - Architecture for demo
• 03:41 - Downloading the installer
• 04:36 - Installing Zabbix Server
• 08:37 - Installing the Zabbix agent
• 12:17 - Applying Qlik specific templates
• 14:28 - Reviewing Qlik-specific Dashboards
• 16:49 - Configuration details
• 18:42 - How to create a dashboard
• 20:30 - Q&A: Can Zabbix run on Windows?
• 21:16 - Q&A: Is Zabbix supported by Qlik?
• 21:36 - Q&A: Can this monitor data capacity?
• 22:45 - Q&A: Can the Zabbix agents affect performance?
• 23:20 - Q&A: Can it monitor bookmark size?
• 24:02 - Q&A: Can this monitor amount of data being used?
• 24:19 - Q&A: Can this monitor sheets, and objects in apps?
• 24:49 - Q&A: Is there a similar tool for Cloud?
• 25:36 - Q&A: Would this work with QlikView?
• 26:11 - Q&A: Does this read the app data?
• 26:26 - Q&A: Can this help measure how long to open an app?

The information in this article and video is provided as is. If you need assistance with Zabbix, please engage with Zabbix directly.

Environment overview

The environment being demonstrated in this article consists of one Central Node and Two Worker Nodes. Worker 1 is a Consumption node where both Development and Production apps are allowed. Worker 2 is a dedicated Scheduler Worker node where all reloads will be directed. Central Node is acting as a Scheduler Manager.

Zabbix Server set-up

The Zabbix Monitoring appliance can be downloaded and configured in a number of ways, including direct install on a Linux server, OVF templates and self-hosting via Docker or Kubernetes. In this example we will be using Docker. We assume you have a working docker engine running on a server or your local machine. Docker Desktop is a great way to experiment with these images and evaluate whether Zabbix fits in your organisation.

Clone the Zabbix docker repository

This will include all necessary files to get started, including docker compose stack definitions supporting different base images, features and databases, such as MySQL or PostgreSQL. In our example, we will invoke one of the existing Docker compose files which will use PostgreSQL as our database engine.

Source: https://www.zabbix.com/documentation/current/en/manual/installation/containers#docker-compose

git clone https://github.com/zabbix/zabbix-docker.git

Setting up environment variables

Here you can modify environment variables as needed, to change things like the Stack / Composition name, default ports and many other settings supported by Zabbix.

cd ./zabbix-docker/env_vars
ls -la #to list all hidden files (.dotfiles)
nano .env_web

In this file, we will change the value for ZBX_SERVER_NAME to something else, like "Qlik STT - Monitoring". Save the changes and we are ready to start up Zabbix Server.

Re-link compose.yaml to our preferred compose file

./zabbix-docker folder contains many different docker compose templates, either using public images or locally built (latest and local tags).

You can run your chosen base image and database version with:

docker compose -f compose-file.yaml up -d && docker compose logs -f --since 1m

Or unlink and re-create the symbolic link to compose.yaml, which enables managing the stack without specifying a compose file. Run the following commands inside the zabbix-docker folder to use the latest Ubuntu-based image with PostgreSQL database:

1. unlink compose.yaml
2. ln -s ./docker-compose_v3_ubuntu_pgsql_latest.yaml compose.yaml
3. Start the Zabbix stack in detached mode with docker compose up -d

If you skip the -d flag, the Docker stack will start and your command line will be connected to the log output for all containers. The stack will stop if you exit this mode with CTRL+C or by closing the terminal session. Detached mode will run the stack in background. You can still connect to the live log output, pull logs from history, manage the stack state or tear it down using docker compose down.

Pro tip: you will be using docker compose commands often when working with Docker. You can create an alias in most shells to a short-hand, such as "dc = docker compose". This will still accept all following verbs, such as start|stop|restart|up|down|logs and all following flags. docker compose up -d && docker compose logs -f --since 1m would become dc up -d && dc logs -f --since 1m.

Logging in for the first time

• By default, the Zabbix Web GUI will be exposed on ports 80/443
• Using tools like Portainer makes Docker stack management easier

Use the IP address of your Docker host: http://IPADDRESS or https://IPADDRESS.

The Zabbix server stack can be hosted behind a Reverse Proxy.

The default username is Admin and the default password is zabbix. They are case sensitive.

Zabbix Agent installation on Windows Server

Download link: https://www.zabbix.com/download_agents, in this case download the Windows installer MSI.

1. Run the installer .msi
2. Leave components unchanged
3. Hostname = your machine hostname, we will have to use the same hostname when adding a Host in Zabbix Server.
4. Zabbix server IP/DNS: IP address or DNS name of your Zabbix Server
5. Agent listening port, the same port will be used when when adding a Host in Zabbix Server.
6. Enable "Add agent location to the PATH" for convenience in the command line
7. Finish installation

Zabbix Server Configuration

Adding the first Server

After Agent is installed, in Zabbix go to Data Collection > Hosts and click on Create host in the top right-hand corner. Provide details like hostname and port to connect to the Agent, a display name and adjust any other parameters. You can join clusters with Host groups. This makes navigating Zabbix easier.

Fig 1: Adding a Host

 

Note: Remember to change how Zabbix Server will connect to the Agent on this node, either with IP address or DNS. Note that the default IP address points to the Zabbix Server.

Importing Qlik Sense Enterprise for Windows templates

In the Zabbix Web GUI, navigate to Data Collection > Templates and click on the Import button in the top right-hand corner. You can find the templates file at the following download link:

LINK to zabbix templates

Linking templates to hosts

Once you have added all your hosts to the Data Collection section, we can link all Qlik Sense servers in a cluster using the same templates. Zabbix will automatically populate metrics where these performance counters are found. From Data Collection > Hosts, select all your Qlik Sense servers and click on "Mass update". In the dialog that comes up, select the "Link templates" checkbox. Here you can link/replace/unlink templates across many servers in bulk.

Select "Link" and click on the "Select" button. This new panel will let us search for Template groups and make linking a bit easier. The Template Group we provided contains 4 individual templates.

Fig 2: Mass update panel

Fig 3: Search for Template Group

Once you Select and Update on the main panel, all selected Hosts will receive all items contained in the templates, and populate all graphs and Dashboards automatically.

To review your data, navigate to Monitoring > Hosts and click on the "Dashboards" or "Graphs" link for any node, here is the default view when all Qlik Sense templates are linked to a node:

Fig 4: Host Dashboards

 

Fig 5: Repository Service metrics - Example

Engine Healthcheck Monitoring with HTTP Agent example

We will query the Engine Healthcheck end-point on QlikServer3 (our consumer node) and extract usage metrics from by parsing the JSON output.

Steps to configure a new HTTP Agent for QSE Health monitoring

We will be using a new Anonymous Access Virtual Proxy set up on each node. This Virtual Proxy will only Balance on the node it represents, to ensure we extract meaningful metrics from the Engine and we won't be load-balanced by the Proxy service across multiple nodes. There won't be a way to determine which node is responding, without looking at DevTools in your browser. You can also use Header or Certificate authentication in the HTTP Agent configuration.

Once the Virtual Proxy is configured with Anonymous Only access, we can use this new prefix to configure our HTTP Agent in Zabbix.

Defining the Virtual Proxy prefix for Zabbix HTTP Agent

In the Zabbix web GUI, go to Data collection > Hosts. Click on any of your hosts. On tabs at the top of the pop-up, click on Macros and click on the "Inherited and host macros" button. Once the list has loaded, search for the following Macro: {$VP_PREFIX}. This is set by default to "anon". Click on "Change" and set Macro value to your custom Virtual Proxy Prefix for Engine diagnostics, and click Update. The Virtual Proxy prefix will have to be changed on each node for the "Engine Performance via HTTP Agent" item to work. Alterantively, you can modify the MACRO value for the Template, this will replicate the changes across all nodes associated to this Template.

To make this change at the Template level, go to Data collection > Templates. Search for the "Engine Performance via HTTP Agent" and click on the Template. Navigate to the Macros tab in the pop-up and add your Virtual Proxy Prefix here to make this the new default for your environment. No further changes to Node configuration are required at this point.

The Zabbix templates provided in this article contain the following Engine metric JSONParsers:

• Memory: Allocated, Committed, Free, Total Physical
• Calls, Selections
• Saturation status (true/false)
• Sessions: Active/Total
• Users: Active/Total

These are the same performance counters that you can see in the Engine Health section in QMC.

Stay tuned to new releases of the Monitoring Templates. Feel free to customise these to your needs and share with the Community.

Resources & Links

• Zabbix home page
• Zabbix Installation from containers documentation
• Zabbix Docker repository on GitHub
• Install Docker Engine on Ubuntu

Environment

• Qlik Sense Enterprise on Windows

A Qlik Sense app has been deleted from the Qlik Sense Management Console and needs to be restored.

! Deleting Qlik Sense application from Qlik Management Console (QMC) is generally an irreversible process. Restoring the applications is only possible if a previous backup exists. The delete process removes all files from the configured file share. See Creating a file share (Help.com).

If a backup of the files exists, proceed with the documented steps.

Note that these steps can also be applied when restoring and importing from one Qlik Sense environment to the other. 

Information on server migration has also be posted to Qlik Community: Qlik Sense Migration Part1: Migrating your Entire Qlik Sense Environment. If assistance is needed, Qlik Consulting would need to be engaged. Qlik Support cannot provide walk-through assistance with server migrations outside of a post-installation and migration completion break/fix scenario.

Resolution:

To successfully restore Qlik Sense Application to the Qlik Sense environment, you must ensure backup strategy using your backup software tool for your shared folder, where Qlik Sense Application files are stored.

! If no backups of files are available, no restoration will be possible. 
 

Restore process:

1. Find the App filename

You can find the filename (APP_ID) in the AuditActivity_Engine log.
This log is by default stored in: \\<rootShare>\Log\Engine\Audit\ by default.

An example showing App id followed by App name follows:


492    20.4.2.0    20180521T180500.118+0200    QlikServer1    0ccd5e9f-e020-4b76-a84d-144bdf903765    20180521T180500.112+0200    12.145.3.0    Command=Reload app;Result=0;ResultText=Success    0    0    2290    INTERNAL    sa_scheduler    d296b870-da06-4311-bacc-038992b1c954    c047d8a7-148c-4ea6-97f2-10290e706cd7    License Monitor    Engine    Not available    Doc::DoReloadEx    Reload app    0    Success    0ccd5e9f-e020-4b76-a84d-144bdf903765
 

2. Add extension ".qvf" to the app file

This will make the file readable and importable. 

• Navigate to the file on disk.
• Right-click and click rename 
• Add .qvf as a file extension
• Confirm any warnings that the file may not be accessible any more after renaming

3. Import the App

• Open the Qlik Sense Management Console
• Go to Apps
• Locate and click Import 

•  Locate the file on disk
• Click Open

• Rename the App to the original name

4. App has been imported and received a new APP_ID

You can now locate the app in the shared folder with a new App ID.

5. Find the proper stream where the app resides

6. Go to section "APPS" select the app, hit "Publish"

Click Publish  

The Publishing dialogue:
 

 

7. Hit "Ok", the app is being published - IMPORTED back

8. The confirmation message should now print as Successful in the App list.

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor, License Monitor, and Content Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

You can automate daily distribution of the latest app using the Capacity consumption app deployer template in Qlik Automate.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor, License Monitor, and Content Monitor

The Operations Monitor loads service logs to populate charts covering the performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor. 

• Basic information can be found in Operations Monitor | help.qlik.com
• Detailed descriptions of sheets and visualizations are accessible in the About the Operations Monitor story available from the app overview page under Stories

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

• Basic information can be found in License Monitor | help.qlik.com  
• Detailed descriptions of sheets and visualizations are accessible in the About the License Monitor story available from the app overview page under Stories

The Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of the platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.

• Basic information can be found in Content Monitor | help.qlik.com  
• Each sheet in the Content Monitor includes an About text box to describe its content. 
  

All three apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor | Content Monitor (download page). Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

Qlik Sense Connectors are missing from the Data source except few REST connectors.

Resolution

Solution 1

Repair Qlik Sense with the Qlik Sense Setup file (identical version).

Solution 2

1. Obtain a copy of the folder "C:\Program Files\Common Files\Qlik\Custom Data\" from a different, but working Qlik Sense Enterprise on a Windows environment (identical version). A test installation can be set up to obtain it.
2. Replace the files/folders with the copied version. This action needs to be carried out on all nodes if it is a multi-node environment.

Solution 3

Encryption keys:

• Verify if the Encryption keys are present in the User's directory.
• Check if you have multiple encryption keys stored in the User's directory.
• Delete and recreate the Encryption keys using Setting an encryption key

Encryption keys will be stored in either "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\" Or "C:\Users\{sense service user}\AppData\Roaming\Qlik\Keys\"

Cause

• The Connector folders or executables are corrupted or deleted.
• Connector folders or executables are being scanned and removed from their path. Therefore, it is mandatory to exclude Qlik folders if any scanning software is present on Qlik Sense Windows machines. For more information about exclusions, please refer to the document titled Qlik Sense Folder And Files To Exclude From Anti-Virus Scanning
• Encryption Keys are either deleted or corrupted.

Related Content

Qlik Sense ODBC Connectors are no longer available after an Upgrade - Error Message Unknown Connection Type. QvOdbcConnectorPackage.exe

An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet

Environment

• Qlik Sense Enterprise on Windows 

According to the Qlik Cloud Platform document, Qlik leverages our cloud providers for backups to maintain copies of content for 30 days.

Can I restore one of those backups?

No, those backups cannot be restored. They are kept for disaster recovery purposes (see Disaster recovery/backup and recovery) and encompass entire regions. 

It's therefore not possible to recover a tenant's previous stage.

It's the tenant admin's responsibility to make sure that copies of the content are regularly backed up on any platform of choice for easy restoration. See Qlik Cloud Administration: Backup Responsibilities for details. 

Environment

• Qlik Cloud Analytics

In some instances, when a user shares a single app using the Share > Invite or Share > Manage Access option, the entire space is shared as well. 

Resolution

There are two possible root causes. Both are triggered by the user not having the correct permissions to share an app, but having permissions to share the space. In this instance, the system defaults to sharing the whole space. 

Qlik is working on an improvement to clarify what you are sharing, meaning you will be alerted you are sharing the space in the future. 

The two scenarios:

• Sharing applications via fine-grained access control is disabled in the User default or for the user.
  
  This affects all spaces.
  
  
  
  To resolve this, either enable it globally or create a custom role that allows the use of fine-grained access control. See Managing custom roles.
  
  
• The user is a tenant admin, allowing them to share spaces, but is not the owner of the space and does not have Can Manage permissions.
  
  This affects specific spaces.
  
  To resolve this, grant the user Can Manage permissions on the space or make them the owner.

  While this is currently by design, Qlik plans to change this behaviour in the upcoming feature to make this action unnecessary.

Environment

• Qlik Cloud Analytics

Qlik Cloud includes robust disaster recovery and backup mechanisms for active tenant data. See Adaptive high-availability infrastructure for details.

However, this does not mean data that has been deleted by the customer is being retained. Any intentionally or accidentally deleted Qlik Cloud data cannot be recovered by Qlik. See Qlik Cloud Analytics: Is it Possible to Recover a Deleted App or Sheet?

To prevent data loss, customers are responsible for implementing their own backup strategy for any content that may be removed. This includes apps, sheets, and spaces within the Qlik Cloud environment.

How to Back Up Qlik Cloud Apps

There are several ways to back up Qlik Cloud content:

• Qlik Automate
• Qlik CLI
• Qlik REST APIs
• Third-party solutions

Qlik Automate

Qlik Automate supports the creation of workflows that regularly back up apps within Qlik Cloud. These workflows can, for example, be configured to export apps to external storage, synchronize content between spaces, or integrate with version control systems.

Here are some helpful resources to get started:

• CI/CD pipelines for Qlik Sense apps with automations and GitHub
• How to export a Qlik Sense app without data to an Amazon S3 bucket and import an app from a file on Amazon S3
• How to export Qlik Sense Apps from source to a target shared space using Qlik Application Automation

These automations can be tailored to meet organizational backup requirements and integrated into broader content management strategies.

Qlik CLI

Qlik CLI enables app exports using command-line tools.

For more information regarding Qlik CLI, please see this introduction on the Qlik Developer Portal.

With Qlik CLI installed, the “qlik app export <appId> [flags]” command can be used to export an app. More information about the command and its available flags can be found on its Qlik Developer Portal page.

Qlik REST APIs

The public Qlik REST APIs can be used to build a more customized, local solution.

Using the POST /api/v1/apps/{appId}/export endpoint returns a "Location" header with the download URL for the exported app.

Third-party solutions

External tools that integrate with Qlik Cloud can also be used to back up apps. Please note that third-party solutions are not supported by Qlik Support.

Environment

• Qlik Cloud

This article provides details about the new permissions available for Private automations, which will replace the previous Automation Creator role.

You can assign these permissions to a custom role or the User Default. More information about creating & managing custom roles is available here.

The existing Automation Creator role will be deprecated later in 2026.

Private automations

These permissions allow users to run and create automations in their personal space.

Shared automations

Earlier in 2025, we introduced the shared automation permission that allows users to run, create, and manage automations in shared spaces in which they have the correct permissions. More information about which space roles are required for the various automation actions is available here:

• Full & Professional users
• Analyzer users

Qlik Talend Cloud tasks do not offer logging at the task level for Storage and further downstream tasks. For those tasks, specifically, support may request Task Event files to troubleshoot various issues, which are especially helpful for troubleshooting downstream tables that are in error or not progressing as expected. Often the event files from the impacted task and its source or predecessor task will be requested.

In this article, we will guide you through how to download the event logs:

1. Navigate task's Monitor tab
   
    

   

2. Place the mouse cursor in the space between the Run button and the task status (such as Running, Completed, Stopped), then:
   
   
   • (on Windows) hold CTRL+ALT and double left-click the mouse
   • (on Mac) hold Command+Option and double left-click the mouse
     
      
      

     

      

3. The downloads will begin automatically and fetch four files:
   
   
   
   For some tasks, the following pop-up will appear. Unless instructed otherwise by Support, click OK:
   
    

   

Environment

• Qlik Talend Cloud

This article explains how to obtain a task schedule in the Talend Management Console, how to pause it, and how to resume it. All steps are performed using the API.

In the example, we use the following values:

• The Environment ID: 5b0431e2ee7c2b4082797c73
• Task ID: 698ba125c327f6c153585c67
• %TOKEN% is to be replaced by your actual bearer's token
• The API URL used in each example is set to the EU region, api.eu.cloud.talend.com. Update the region accordingly. 
• The schedule is set from: 1772628971000 to 1775220971000, which is the 3rd of March 2026 to the 3rd of April 2026 in milliseconds since January 1st 1970. Use epochconverter.com to convert date and time to epoch time. 

Content

• Getting a task schedule
• Pausing a task
• Resuming a task
• Pausing and resuming a plan

Getting a task schedule

First, we get the scheduling of a task. 

The following Qlik Talend API can be used to retrieve the executions scheduled in a time window using the "from" and "to" parameters: Get scheduled executions 

Get scheduled executions of all types

POST /orchestration/executables/events/search

Example: 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

The API returns a maximum of 100 entries by default. The parameter "offset" can be used to retrieve the next entries.

Example with "offset": 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\",\"offset\":100}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

To retrieve all the entries, increase the "offset" value to the total value returned by the call that is lower than the limit value.

Pausing a task

Next, we pause the task.

The following Qlik Talend API can be used to pause a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":true,\"pauseContext\":\"Pause during the maintenance window\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Resuming a task

We now set the task to resume.

The following Qlik Talend API can be used to resume a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":false}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Pausing and resuming a plan

To pause and resume a plan, the following Qlik Talend API can be used: Pause-Resume Plan executions

Pause-Resume Plan executions

PUT /orchestration/executables/plans/{planId}/pause

Environment

• Qlik Talend Cloud
• Qlik Talend Management Console

A newly created user in Talend Cloud may not receive the expected welcome email if the user was created in the Qlik Talend Management Console. 

Other email notifications are received correctly, such as when resetting an existing user account. 

Resolution

The issue is typically related to role permissions, email notification settings, or SSO configuration in the Qlik Talend Cloud Management Console.

1. Verify User Role Permissions
   
   The account used to create the new user must have the Infrastructure Administrator role. Without this role, the user creation may succeed, but notification emails will not be triggered.
   
   
2. Verify Email Notification Settings
   
   

   Ensure that the “User has been created” notification is selected:

   1. Log in to Talend Cloud Management Console
   2. Go to Profile preferences and then the Notifications option
   3. Confirm that “User has been created” is selected
      
      
      
      If this notification is not selected, no email will be sent when a new user is created.
      
      
3. Check SSO Configuration (Important)
   
   

   If Single Sign-On (SSO) is enabled for Talend Cloud, newly created users will not automatically receive activation emails.

   To trigger the notification email:

   1. Temporarily disable SSO. SSO can be disabled by navigating to the Qlik Talend Management Console > Users > Authentication
   2. After disabling SSO, create the user
   3. Click "Send Invitation” to activate the user account
   4. Once SSO is disabled and the invitation is sent, the notification email will be delivered correctly.

Related Content

• Talend Management Console email notifications 
• Enabling email notifications

Environment

• Qlik Talend Cloud
• Qlik Talend Management Console

Qlik Sense may be unable to access the Qlik Sense Management Console (QMC) and/or HUB. You will find below some guidance explaining how to troubleshoot those.

To start your troubleshooting you will need to clearly identify your issue: 

• Is the issue only regarding the HUB?
• Is the issue only regarding the QMC?
• Is the issue regarding both the QMC and the HUB?

In this troubleshooting guide we will talk about the third scenario where you are unable to open neither the Qlik Sense Management Console (QMC) and the HUB

As a second steps to identify your issue, you will need to answer the three following questions:

• Is this issue has started occurring after a fresh installation or an upgrade of the product without having worked before?
• Is this issue occurring on a random basis from time to time? 

We will discuss the following two scenarios below.

Below is a provided list of article containing specific root causes that that could help you after following the above steps: 

No Hub or QMC access after upgrade to Sense November 2017 or higher - recursive script
How to approach Qlik Sense Error 404 when access Hub/QMC
Qlik Sense: Cannot access QMC or Hub. Error in repository log: implementation not part of Windows FIPS validated cryptographic algorithms
Qlik Sense Installation successful but problem opening QMC/HUB
Can't access Qlik Sense QMC or HUB using local service account
Cannot open Qlik Sense Management Console or hub after upgrade - RootFolder and AppFolder are not defined at startup 
Qlik Sense Management Console (QMC) and Hub are not accessible and connection to QRS Database times out after 90 seconds 

Resolution

General verification

Before starting to investigate deeper into the issue you need to apply some basic steps to troubleshoot:

• Verify general network connectivity. Qlik Sense relies on the usage of WebSockets, which may be blocked. See How to troubleshoot web socket issue for Qlik Sense? for details. 
• Are you following the minimal requirements (Please make sure you select the correct version). 
• Are the Qlik Sense services up and running? => Try to start and restart them to see if it comes back up and running. (You might need to wait a few minutes before the services become operational)
• Are you using the correct URL to access the Qlik Sense Management (QMC) and HUB? => You can try to access them connected remotely to the Qlik Sense Server by accessing the URL https://localhost/qmc or https://localhost/hub. If this works you might have a DNS and/or a network issue.
• Do you have connectivity to the Qlik Sense Server from the machine you are attempting to connect?  Verify with a network ping and/or telnet to Qlik Sense on the relevant ports. Please see How To Check Open Ports Using PowerShell and the relevant version help site.  

The issue has started occurring after a fresh installation or an upgrade of the product without having worked before

If after checking the above points you still experience issues, you need to know that to start properly, the Qlik Sense Management Console will need to have few services properly working: 

• The Qlik Sense Repository Database
• The Qlik Sense Repository Service
• The Qlik Sense Dispatcher
• The Qlik Sense Proxy

To verify if those services are actually functioning correctly, you will need to check their logs.
Start by looking into the Qlik Sense Repository logs stored by default in C:\Programdata\Qlik\Sense\Log\Repository\Trace\Servername_System_Repository.txt. (You might want to restart the services before looking into this log to get fresh information)

If the Qlik Sense Repository Database and Service starts correctly you are basically looking at the following string in this logs (It might take few minute to initialize after a service restart)
Startup phase completed

If you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in this logs. You can then grab the content of the message and search it in our knowledge base

However if you find this string in the logs, the next step is to check the Qlik Sense Proxy logs stored by default in C:\Programdata\Qlik\Sense\Log\Proxy\Trace\Servername_System_Proxy.txt
Once again we would recommend to restart the Qlik Sense Proxy Service before looking into the logs to get fresh information.

In this log you might see few errors at the beginning saying
When contacting https://localhost:4242/    No connection could be made because the target machine actively refused it 127.0.0.1:4242
Could not contact local repository to retrieve local server node configuration    No connection could be made because the target machine actively refused it 127.0.0.1:4242

Those will be expected since the Qlik Sense Proxy service will try to connect to the Qlik Sense Repository Service, so as long as the startup phase is not completed for the Qlik Sense Repository service you will keep getting those events in the logs.
Basically if the Qlik Sense Proxy service is starting correctly you should expect the following event in the logs: 

Proxy is running

As for the Qlik Sense Repository if you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in these logs. You can then grab the content of the message and search it in our knowledge base.

E.g. Here is an example of the types of error you can get in the Qlik Sense logs: 

Proxy will NOT be listening to port 443, likely bound by another process An attempt was made to access a socket in a way forbidden by its access permissions.

The above steps should help you to investigate the root cause of your issue for this scenario.

The issue occurs on a random basis from time to time

In the following scenario we are more looking into an environment issue such as network connectivity, resource overload, ...
The first step would be to check the Qlik Sense Repository Service and Proxy logs as described above to find any relevant ERROR and/or WARN that could explain the root cause. 

Then you can start looking into the Windows Event logs (Application and System) to find any problem at a system level around the time you are getting this issue.

Below are common causes/events that you could find in those logs: 

• Memory starvation Windows successfully diagnosed a low virtual memory condition?
• Network issue The network link is down.  Check to make sure the network cable is properly connected

Those types of event require often to involve your system and/or network and/or virtualization team for further troubleshooting.

In addition you can run a performance monitor to check the resource consumption on your machine following How to log CPU and memory with Microsoft Performance Monitor on a windows 2012 Server (PerfMon)

 

Understanding and managing your Qlik Cloud subscription consumption is essential for maintaining predictable costs, ensuring uninterrupted service, and optimizing resource allocation across your organization. This guide provides you with the tools, strategies, and best practices to gain complete visibility into how your subscription is being consumed and implement proactive controls to stay within your capacity limits.

While Qlik Cloud measures consumption at the tenant level, you can achieve effective governance through strategic monitoring, automated alerting, and space-based management practices. This guide will walk you through the monitoring tools available, how to automate their deployment and refresh, and practical approaches to tracking consumption patterns and implementing controls that align with your organizational needs.

Content:

• Understanding the Administration activity center capacity consumption view
• The Home page capacity consumption dashboard
• How does this view fit into your monitoring strategy?
• Official consumption data: The Data Capacity Reporting App
• Automating the deployment of the consumption app
• Getting estimated usage with Qlik Cloud Monitoring Apps
• Automating Qlik Cloud Monitoring Apps deployment
• Proactive monitoring strategies: What to track and at what levels
• Monitoring automation runs
• Monitoring Data for Analysis
• Monitoring scheduled reloads
• Monitoring reports generated
• Practical approaches to controlling consumption
• 1. User education and communication
• 2. Alert-driven intervention workflow
• 3. Development vs. production separation
• Leveraging Qlik's alerting and distribution capabilities for consumption monitoring
• Available monitoring and distribution tools
• Setting up each monitoring approach
• Examples: Setting up consumption monitoring across key metrics
• Your action plan: From reactive to proactive
• Additional resources

Understanding the Administration activity center capacity consumption view

The Administration activity center Home page provides your first line of visibility into capacity consumption. Understanding what this view offers and how it complements the detailed monitoring apps will help you build an effective monitoring strategy.

The Home page capacity consumption dashboard

Navigate to the Administration activity center → Home to see a real-time dashboard summarizing capacity consumption. This view displays visual bar charts for consumption metrics relevant to your subscription:

Common metrics displayed:

• Data for Analysis: Purchased vs. used with color-coded breakdown (App Import, App Reload, Datafile); not available for user-based subscriptions
• Reports generated (monthly): Purchased count vs. used
• Standard automation runs (monthly): Purchased vs. used
• Third-party automation runs (monthly): Purchased vs. used
• Assistant questions asked (monthly): Purchased vs. used (if Qlik Answers is enabled)

Additional metrics may include Data Moved, Large App consumption, Qlik Predict deployed models, and others, depending on your subscription.

Metrics appear dynamically as features are adopted. If no one has asked an assistant question yet, that metric won't display until first use, keeping the dashboard focused on what you're consuming.

The Data for Analysis chart shows a current snapshot with the last update timestamp. Most metrics update multiple times per hour, providing near real-time visibility into your consumption position.

How does this view fit into your monitoring strategy?

The Administration activity center provides high-level consumption visibility designed for rapid assessment. For detailed analysis, investigation, and proactive monitoring, you'll complement this view with a set of monitoring apps.

Daily quick check (2 minutes):

1. Scan consumption bars to identify any metrics approaching capacity
2. Review indicators showing current usage levels
3. Verify Data for Analysis timestamp shows recent data

When you need more detail, the Home page tells you what is being consumed. The monitoring apps tell you who, where, when, and why. Capacity subscriptions should use the Data Capacity Reporting App as the source of truth, while the Qlik Cloud Monitoring apps can be treated as estimated consumption reports, for example:

• For automation consumption details: Use the Automation Analyzer
• For data consumption details: Use the Data Capacity Reporting App and Reload Analyzer
• For report consumption details: Use the Report Analyzer

Use the Home page for daily checks and status awareness. When consumption requires attention or you need to understand trends, drill into the appropriate monitoring app for detailed analysis.

For more information, see Monitoring resource consumption.

Official consumption data: The Data Capacity Reporting App

The Data Capacity Reporting App is your official, billable record of consumption for capacity-based subscriptions. This Qlik-supported application is generated once per day (morning Central European Time) and provides the definitive view of your consumption against your entitlement.

The app tracks eight key value meters across the current and previous two months:

• Data for Analysis: Total data loaded into or created in Qlik Cloud (measured by monthly peak usage)
• Data Moved: Volume of data moved to cloud destinations via Qlik Talend Data Integration
• Third Party Transformations: Datasets used in transformations but not delivered by Qlik Talend Data Integration
• Automation Runs: All automation executions using Qlik Automate
• Reports: Reports distributed using Qlik Reporting Service
• Job Executions: Number of Talend job task runs (Qlik Talend Cloud subscriptions)
• Job Duration: Total duration of Talend job executions (Qlik Talend Cloud subscriptions)

This app represents your billable consumption record. The data in this app is what Qlik uses for official capacity reporting and billing purposes. When there's any discrepancy between this app and other monitoring sources, the Data Capacity Reporting App is the authoritative source. This app refreshes only once daily, meaning you see yesterday's official position, not real-time consumption. For more frequent monitoring and estimated usage, you'll complement this with the Qlik Cloud Monitoring Apps.

For detailed information, see Monitoring detailed consumption for capacity-based subscriptions.

Automating the deployment of the consumption app

Rather than manually distributing the consumption app from the Administration activity center each day, automate this process using the Capacity consumption app deployer template in Qlik Automate.

Setup steps:

1. Create a new automation in Qlik Automate
2. Navigate to the App Installer category
3. Select "Capacity consumption app deployer" template
4. Configure variables (space names, versions to keep)
5. Test manually once
6. Schedule to run daily around midday CET

This automation creates or uses designated spaces, imports the latest version, publishes it to a managed space, and maintains version history according to your configuration. You now have a single source of truth that updates automatically each day. Create automations or alerts on the published app for automated insights.

For complete details, see the Qlik Community article: Automate deployment of the Capacity consumption app with Qlik Automate.

Getting estimated usage with Qlik Cloud Monitoring Apps

While the official consumption report updates once daily, the Qlik Cloud Monitoring Apps (community-supported) can be reloaded multiple times per day up to your contractual reload limits, giving you more timely estimated usage insights.

The Qlik Cloud Monitoring Apps provide estimated consumption data that may differ slightly from the official Data Capacity Reporting App. Use these apps for trend monitoring, troubleshooting, and proactive management, but always refer to the Data Capacity Reporting App for official billable consumption figures.

Particularly valuable monitoring apps include:

App Analyzer: Provides comprehensive application usage and operational analytics, including:

• App access patterns and session frequency by user
• Sheet and object usage tracking
• App metadata and lineage information
• Historical snapshots to track changes over time

Automation Analyzer: Provides detailed analysis of automation runs, including:

• Run frequency by automation, space, and user
• Success/failure rates and error patterns
• Execution duration trends
• Third-party block usage tracking

Reload Analyzer: Tracks data refresh activity, including:

• Reload frequency by app and space
• Duration and resource consumption
• Success rates and failure patterns
• Reload scheduling patterns

Access Evaluator: Analyzes user roles, access, and permissions across your tenant

Report Analyzer: Tracks report generation, including:

• Report task execution frequency
• Report distribution patterns
• Report generation consumption

Entitlement Analyzer: For user-based subscriptions, provides insights into:

• Professional and Analyzer seat allocation and utilization
• Analyzer capacity consumption by user (for Analyzer capacity licenses)
• User session patterns and license assignment

For a complete list of available monitoring apps, see the Qlik Community article: The Qlik Sense Monitoring Applications for Cloud and On-Premise.

Automating Qlik Cloud Monitoring Apps deployment

The Qlik Cloud Monitoring Apps deployer template simplifies installation and maintenance of these community apps.

What it handles:

• Installs/upgrades selected monitoring apps from Qlik's OSS GitHub
• Creates required API keys and data connections
• Manages API key rotation to ensure connections remain operational
• Creates or uses existing shared and managed spaces
• Schedules regular reloads (configurable frequency)
• Verifies prerequisite settings and notifies if configuration changes are needed

Reload frequency considerations: You can reload these monitoring apps multiple times per day to get more current estimated usage data. However, each reload counts against your tenant's reload capacity limits. Consider your contractual limits when scheduling. For most organizations, reloading 2-4 times per day provides a good balance between timely insights and consumption.

For complete implementation details, see the Qlik Community guide: Qlik Cloud Monitoring Apps Workflow Guide.

The monitoring apps are also available on GitHub: qlik-oss/qlik-cloud-monitoring-apps.

Proactive monitoring strategies: What to track and at what levels

Effective governance comes from monitoring consumption at multiple levels and implementing proactive interventions. Here's how to approach monitoring for key consumption metrics.

Monitoring automation runs

Automation runs are counted across all automations in your tenant, regardless of owner or run mode (manual, scheduled, triggered, webhook, API). Test runs within the automation editor also count toward your limit.

What to monitor:

Tenant level:

• Total automation runs per month against your purchased capacity
• Rate of consumption (tracking whether you're on pace to exceed limits)
• Third-party block usage (may incur additional costs depending on subscription)

Space level:

• Which spaces are generating the most automation runs
• Identify spaces with unusually high consumption

Automation level:

• Individual automation run frequency
• Failed runs that retry excessively
• Scheduled vs. triggered vs. webhook run distribution

User level:

• Which users own the most frequently running automations
• Users with failed automations requiring attention

Example alert scenario: Using the Automation Analyzer, create alerts when:

• Total third-party (billable) runs reach 80% of purchased capacity
• Any single automation runs more than 100 times per day
• Failed run rate exceeds 20% for any automation
• A specific space's automations account for more than 40% of total runs

Monitoring Data for Analysis

Data for Analysis is measured by monthly peak usage. A single day's spike can impact your entire month's consumption.

This data is only available via the Data Consumption report; it is a lagging metric and currently lacks customer data such as app names, user names, and space names. As such, use of an automation template to provide notifications may be preferable to standard alerts, and some app size metrics may be better analyzed in the reload analyzer.

What to monitor:

Tenant level:

• Daily peak compared to purchased capacity
• Trend analysis: Are daily peaks increasing?
• Current month peak vs. previous months

App level:

• Which apps are contributing most to data volume
• New apps that significantly increase consumption
• Apps with unexpectedly large data reloads

Space level:

• Data consumption by space

Example alert scenario: Using the Data Capacity Reporting App and Reload Analyzer:

• Alert when the daily peak reaches 80%, 90%, 95% of purchased capacity in the Data Capacity Reporting App
• Alert when any single app reload increases data volume by more than 20GB in the Reload Analyzer
• Alert when a space's total data exceeds a defined threshold in the Data Capacity Reporting App

Monitoring scheduled reloads

Each subscription tier has limits on maximum concurrent reloads, and capacity subscriptions have daily reload counts. Exceeding concurrent limits causes queuing; exceeding daily limits can block operations.

What to monitor:

Tenant level:

• Scheduled reloads that exceed contractual limits
• Concurrent reload patterns during peak hours
• Failed reload rate

Space level:

• Reload frequency by space (wasted work)
• Reload schedule overlap that causes queuing

App level:

• Apps with multiple reload tasks
• Apps with long-running reloads that block concurrency

Example alert scenario: Using the Reload Analyzer:

• Alert when an app has more than one reload task active
• Alert when failed reloads exceed 10% in any 24-hour period
• Alert when reload queuing occurs during business hours

Monitoring reports generated

Report generation counts vary by subscription tier, with add-on packs available for purchase. Across all reporting capabilities, tenants have a maximum of 30,000 reporting-related requests per day.

What to monitor:

Tenant level:

• Monthly report generation against purchased capacity
• Rate of consumption throughout the month

Report task level:

• Which report tasks generate the most reports
• Report tasks using cycling (can generate up to 500 unique reports per task)

Example alert scenario: Using consumption reporting and monitoring apps:

• Alert when monthly reports reach 75% of capacity
• Alert when any single report task generates more than 100 reports in a day
• Alert when daily reporting requests approach 25,000

For detailed information on report limits, see Qlik Reporting Service specifications and limitations.

Practical approaches to controlling consumption

While Qlik Cloud measures consumption at the tenant level, you can implement effective governance practices that provide meaningful control over resource usage.

1. User education and communication

Make users aware of the impacts of their consumption and empower them to monitor their own usage.

Implementation:

• Publish monitoring apps to managed spaces accessible by content creators
• Regular communications showing tenant-wide consumption status to creators

2. Alert-driven intervention workflow

Create early warning systems that trigger well before official capacity notifications.

Implementation:

Alert tier 1 (60-70% of capacity):

• Notification to admins and space owners & managers
• Review consumption trends
• Identify optimization opportunities

Alert tier 2 (75-85% of capacity):

• Formal review meeting
• Suspend non-critical scheduled executions (automation runs, assistants, reload tasks, report tasks, etc)
• Contact the account manager about potential overage

Alert tier 3 (90%+ of capacity):

• Disable non-essential executions (automation runs, assistants, reload tasks, report tasks, etc)
• Defer development/testing activities to next month
• Discussion about capacity expansion or overage management

3. Development vs. production separation

Use strict space controls to prevent development consumption from impacting production limits, or procure a development subscription from Qlik to fully isolate capacity.

Implementation:

• Create clear development space boundaries
• Limit development automation runs through governance
• Schedule development reload activities during off-peak hours
• Regular cleanup of abandoned development content

For information on subscription types and capacity planning, see Qlik Cloud capacity-based subscriptions.

Examples: Setting up consumption monitoring across key metrics

The following examples demonstrate how to set up comprehensive monitoring for different consumption metrics. These examples assume you have deployed the Capacity consumption app deployer (running daily around midday UTC) and the Qlik Cloud Monitoring Apps deployer (running overnight) with default settings.

Explore the apps to discover a wide range of operational metrics you can monitor, alert, automate, and subscribe to.

Example 1: Third-party automation runs monitoring and alerts

Scenario: Your organization uses third-party automation blocks (such as Slack, ServiceNow, or Salesforce connectors), which incur additional costs based on consumption. You need to monitor third-party automation runs to prevent unexpected charges and identify which automations are driving costs.

Navigate to the Automation Analyzer and create the following alerts:

Alert 1: Third-party runs approaching limit

• Location: Create on the "Run Quotas" chart in the "Dashboard" sheet by right-clicking on the Billable bar. This will create an alert with three useful measures present:
  
  
  
  
• Condition: "Runs Billable Remaining (Bar)" Less than 2000 (for example):
  
  
  
  
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Alert 2: Individual user excessive third-party runs

• Location: On the "Dashboard" sheet, open the "Runs by executor" tab, and create an alert from this table.
• Condition: Where "Runs Billable CMTD" is Greater than 1000 (or a reasonable limit for an individual user in the tenant):
  
  
  
  
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Automation - Automation usage notifier: Automation or user email notifications

This approach allows you to send email notifications or take action directly on executing users or owners, while sending a fully customised template to notify them that they are approaching limits.

See Automation Usage Notifier | GitHub for details.

• Location: Create a new automation by importing the JSON file provided at automationNotifier. There is a readme present there, in summary:
  • Monitors automation run usage against tenant quota
  • Works directly with the Automation Analyzer monitoring app
  • Supports threshold limits by (automatic lowest-limit enforcement):
    • Absolute run count
    • Percentage of licensed quota
  • Assessment modes:
    • Per automation (notify owners)
    • Per user (notify heavy users)
  • Automatic fallback notification to admin group for orphaned automations or deleted users
  • Rich HTML email alerts with direct automation links
  • Safe to schedule daily or trigger after analyzer reload
  • Fully configurable via simple variables
  • Designed for soft governance and early quota protection

Example 2: Data for Analysis capacity monitoring

Scenario: Your Data for Analysis consumption is measured by monthly peak usage. You need early warning when daily peaks are trending upward and visibility into which apps are driving consumption.

Step 1: Create peak usage alerts in the Data Capacity Reporting App

Alert 1: Warning capacity threshold

• Location: Create on the "Data for Analysis" current month peak usage chart
• Condition: Set "Capacity remaining" to Less than 0.3 (for 30%; adjust to business need)
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Alert 2: Critical capacity threshold

• Location: Create on the "Data for Analysis" current month peak usage chart
• Condition: Set "Capacity remaining" to Less than 0.15 (for 15%; adjust to business need)
• Schedule: When data changes
• Share with others: Add other key administrators/ managers

Step 2: Create a weekly trend subscription

In the Data Capacity Reporting App:

1. Create a sheet showing: Weekly peak trend (last 8 weeks), Top 10 apps by data volume, Space breakdown
2. Create a subscription
3. Schedule: Monday at 9:00 AM
4. Recipients: Administrators, managers
5. Format: PDF
6. Name: "Weekly Data for Analysis consumption report."

Example 3: Comprehensive monthly consumption review package

Scenario: You want to create a comprehensive monthly review package that combines official billable data with estimated usage trends to facilitate informed capacity planning discussions.

Create a Qlik Automate automation that runs on the first business day of each month:

1. Trigger: Scheduled monthly on the first weekday at 9:00 AM
2. Block 1: Generate a snapshot from the Data Capacity Reporting App using the Qlik Reporting connector:
   • All value meters with official consumption vs. purchased capacity
   • Month-over-month trends
   • Year-to-date comparison
3. Block 2: Generate a snapshot from Automation Analyzer using the Qlik Reporting connector:
   • Top 10 consuming automations
   • Executor breakdown
   • Space breakdown
4. Block 3: Generate snapshot from Reload Analyzer using the Qlik Reporting connector:
   • Top 10 apps by reload duration
   • Reload frequency analysis
   • Failed reload summary
5. Block 4: Compile snapshots into a single PDF or PowerPoint
6. Block 5: Distribute to stakeholder group via email

Your action plan: From reactive to proactive

The key to managing Qlik Cloud consumption effectively is shifting from reactive (waiting for 80%/90%/100% notifications) to proactive (continuous monitoring with early intervention).

This week:

• Deploy the Capacity consumption app deployer automation (if on a capacity-based subscription)
• Deploy the Qlik Cloud Monitoring Apps deployer automation with your selected monitoring apps
• Review the deployed monitoring apps and familiarize yourself with available metrics
• Set up your first consumption alert targeting your highest-risk metric

This month:

• Configure a comprehensive tiered alert system across all relevant consumption metrics
• Establish consumption targets for high-usage spaces or functions
• Create documentation for users on consumption best practices
• Conduct the first monthly consumption review meeting

Ongoing:

• Daily: Quick review of the Administration activity center Home page for the current status
• Weekly: Review of alert notifications and trend analysis in monitoring apps
• Monthly: Formal consumption review meeting with stakeholders
• Quarterly: Comprehensive audit of automations, apps, and reload schedules to identify optimization opportunities
• Continuous: Regular communication with users about consumption practices and organizational targets

By combining automated monitoring through the official Data Capacity Reporting App and community monitoring apps, tiered alerts, clear governance policies, and proactive intervention workflows, you can effectively manage your subscription costs and maintain predictable, controlled consumption across your organization.

Additional resources

Qlik Help documentation:

• Monitoring resource consumption
• Monitoring detailed consumption for capacity-based subscriptions
• Qlik Cloud capacity-based subscriptions
• Understanding the subscription value meters
• Managing automations
• Qlik Automate limitations
• Qlik Reporting Service specifications and limitations

Qlik Community Official Support Articles:

• The Qlik Sense Monitoring Applications for Cloud and On-Premise
• Qlik Cloud Monitoring Apps Workflow Guide
• Automate deployment of the Capacity consumption app with Qlik Automate

Developer resources:

• Monitor your deployment (Qlik Developer Portal)
• Qlik Cloud Monitoring Apps on GitHub

The Qlik Cloud Monitoring Apps are community-supported and provided as-is. They are not officially supported by Qlik, though they are maintained through Qlik's Open-Source Software GitHub. The Capacity consumption app deployer and Qlik Cloud Monitoring Apps deployer are supported automation templates found in the template picker catalog.

The Qlik Sense Mobile app allows you to securely connect to your Qlik Sense Enterprise deployment from your supported mobile device. This is the process of configuring Qlik Sense to function with the mobile app on iPad  / iPhone.

This article applies to the Qlik Sense Mobile app used with Qlik Sense Enterprise on Windows. For information regarding the Qlik Cloud Mobile app, see Setting up Qlik Sense Mobile SaaS. 

Content:

• Pre-requirements (Client-side)
• Configuration (Server-side)
• Update the Host White List in the proxy
• Configuration (Client side)

Pre-requirements (Client-side)

See the requirements for your mobile app version on the official Qlik Online Help > Planning your Qlik Sense Enterprise deployment > System requirements for Qlik Sense Enterprise > Qlik Sense Mobile app

Configuration (Server-side)

Acquire a signed and trusted Certificate.

Out of the box, Qlik Sense is installed with HTTPS enabled on the hub and HTTP disabled. Due to iOS specific certificate requirements, a signed and trusted certificate is required when connecting from an iOS device. If using HTTPS, make sure to use a certificate issued by an Apple-approved Certification Authority.
Also check Qlik Sense Mobile on iOS: cannot open apps on the HUB  for issues related to Qlik Sense Mobile on iOS and certificates.

For testing purposes, it is possible to enable port 80.

(Optional) Enable HTTP (port 80).

1. Open the Qlik Sense Management Console and navigate to Proxies.
2. Select the Proxy you wish to use and click Edit Proxy.  
3. Check Allow HTTP 

Update the Host White List in the proxy 

If not already done, add an address to the White List:

1. In Qlik Management Console, go to CONFIGURE SYSTEM -> Virtual Proxies
2. Select the proxy and click Edit
3. Select Advanced in Properties list on the right pane
   
   

    

4. Scroll to Advanced section in the middle pane
5. Locate "Allow list"
   
   

    

6. Click "Add new value" and add the addresses being used when connecting to the Qlik Sense Hub from a client. See How to configure the WebSocket origin allow list and best practices for details. 
   
   

Generate the authentication link:

An authentication link is required for the Qlik Sense Mobile App.

1. Navigate to Virtual Proxies in the Qlik Sense Management Console and edit the proxy used for mobile App access
2. Enable the Client authentication link menu in the far right menu.
3. Generate the link.

NOTE: In the client authentication link host URI, you may need to remove the "/" from the end of the URL, such as http://10.76.193.52/ would be http://10.76.193.52 

Associate User access pass

Users connecting to Qlik Sense Enterprise need a valid license available. See the Qlik Sense Online Help for more information on how to assign available access types.
Qlik Sense Enterprise on Windows > Administer Qlik Sense Enterprise on Windows > Managing a Qlik Sense Enterprise on Windows site > Managing QMC resource > Managing licenses

• Managing professional access
• Managing analyzer access
• Managing user access
• Creating login access rules

Configuration (Client side)

1. Install Qlik Sense mobile app from AppStore.
2. Provide authentication link generated in QMC
   • Open the link from your device (this can be also done by going to the Hub, clicking on the menu icon at the top right and selecting "Client Authentication"), the installed application will be triggered automatically, and the configuration parameters will be applied.
   •  Enter user credentials for QS server

After upgrading from Windows 10 to Windows 11, or applying certain patches to Windows Server 2016, Qlik Replicate may not load in the browser.

The following error is displayed:

ERR_SSL_KEY_USAGE_INCOMPATIBLE

Data Integration Products November 2021.11 or lower require a manual generation of SSL certificates for use. See Step 5 (options one and two) in the solution provided below.

Environment

Qlik Replicate 2022.11 (may happen with other versions)
Qlik Compose 2022.5 (may happen with other versions)
Qlik Enterprise Manager 2022.11 (may happen with other versions)
Use of the self-signed SSL certificate
Windows 11
Windows server 2016

Resolution

This issue has to do with the self-signed SSL certificate. Deleting the existing one and allowing Qlik Replicate/Compose/Enterprise Manager to regenerate them resolves the issue.

1. Stop the services for all affected software. Example: AttunityReplicateUIConsole, Qlik Compose or Qlik Enterprise Manager.
2. (This step only applies to Qlik Replicate) Rename the data folder under the SSL folder (\Program Files\Attunity\Replicate\data\ssl\data)
3. Delete self-signed certificates in the management console
   1. Open a command prompt and enter MMC to open the console (on Windows Server, open "Manage computer certificates")
   2. Click the File drop-down menu and select Add/Remove snap-in
      

      
      

   3. Select Certificates and click Add
      

      
      

   4. Select Computer account. Click Next, then click Finish.
      
      

      

   5. Click OK to close the Add or Remove Snap-ins window
   6. Open Certificates and navigate to Local Computer, then Personal, then Certificates
      
      

      

   7. In the list of certificates shown, select the certificates where the "Issued To" value and the "Issued By" value equal your computer name and delete them.
   8. Close the Management Console.
      
      
4. Next we will remove the reference to the self-signed certificate in Qlik Replicate:
   
   
   1. Open a command prompt As Administrator
      
      For Qlik Replicate:
      
      Navigate to the ..\Attunity\Replicate\bin directory and then run the following command:
      
      RepUiCtl.exe certificate clean
      

      
      
      
      For Qlik Compose:

      Navigate to the ..\Qlik\Compose\bin directory and then run the following command:
      
      ComposeCtl.exe certificate clean
      
      

      For Qlik Enterprise Manager:

      Navigate to the ..\Attunity\Enterprise Manager\bin directory and then run the following command:
      
      aemctl.exe certificate clean
      
      
   2. Run the command: netsh http delete sslcert ipport=0.0.0.0:443
      
      Note, that you may get a message that the command failed in the event there are no certificates bound to the port. This message can be ignored.
      
      
5. Add either a self-signed Certificate or a trusted and signed Organization Certificate.
   
   Option One: Trusted and Signed Certificate. Generate an organization certificate that must be a correctly configured SSL PFX file containing both the private key and the certificate.
   
   Option Two: Self-Signed Certificate. Generate a self-signed certificate on the server to replace the existing self-signed certificate. The provided PowerShell examples generate an SSL certificate for 10 years.
   
   Run the following in PowerShell:
   
   $cert = New-SelfSignedCertificate -certstorelocation cert:\localmachine\my -dnsname <FQDN> -NotAfter (Get-Date).AddYears(10)
   
   
6. Once the certificates have been obtained or generated, follow the instructions for the individual product section on how to import a certificate:
   
   
   • Qlik Enterprise Manager: Replacing the self-signed certificate on Windows 
   • Qlik Replicate: Setting Up Qlik Replicate Server HTTPS support 
   • Qlik Compose: Replacing the self-signed certificate on Windows 
     
     
7. Start the services.
8. You may need to clear browser cache/cookies & etc. before you can access the web page outside of incognito mode.

Qlik Replicate will now allow you to open the user interface once again.

If users still cannot log in and are returned to the log in prompt at each attempt, see How to change the Qlik Replicate URL on a Windows host.

It is recommended to use your organization certificates  

Related Content:

How to change the Qlik Replicate URL on a Windows host 

Google Chrome Community

Microsoft Answers

Changing the IP address of the Qlik Sense host does not require as much consideration as changing the host name. Some external components might need to be taken into account though. 

Using an IP address as the hostname while installing Sense is not recommended and can lead to problems with service communication. Refer to While accessing Hub receive error "The service did not respond or could not process the request" .

Environment: 

Resolution:

Things to consider:

• In the PostgreSQL database, an listening_addresses might have been set up during the installation. See PostgreSQL: postgres.conf and pg_hba.conf explained for details. 
• Outside configuration steps might need to be taken, such as updating DNS records or firewall rules.
• SAP connector considerations: Ensure that the SAP server is contactable by the new Sense server IP address and the SAP server allows connections from the new Sense IP address.
• Other outside connectors may also operate based on IP allowlist.

Related content:

• How to identify end user Client Browser, OS, Device and IP address in Qlik Sense

• Qlik Sense: Change hostname (and certificates) after an installation

Environment

• Qlik Sense Desktop
• Qlik Cloud Analytics