How to take control of your Qlik Cloud subscription: a guide to monitoring and managing consumption

Dave_Channon — Tue, 17 Feb 2026 06:15:43 GMT

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 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):

Scan consumption bars to identify any metrics approaching capacity
Review indicators showing current usage levels
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:

Create a new automation in Qlik Automate
Navigate to the App Installer category
Select "Capacity consumption app deployer" template
Configure variables (space names, versions to keep)
Test manually once
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.

Leveraging Qlik's alerting and distribution capabilities for consumption monitoring

Now that you have the monitoring apps deployed and refreshed regularly, you can leverage Qlik Cloud's built-in alerting and distribution capabilities to create a proactive monitoring system. These tools transform static consumption data into actionable intelligence that reaches the right people at the right time.

Available monitoring and distribution tools

Data Alerts: Create threshold-based alerts that evaluate conditions on a schedule and notify recipients when conditions are met. Alerts can be created on any chart or measure in your monitoring apps and can be shared with users or groups. Inclusive in all plans.

Subscriptions: Schedule automatic distribution of charts, sheets, or entire apps to users via email or Microsoft Teams. Subscriptions ensure stakeholders receive regular consumption reports without needing to log into Qlik Cloud. Inclusive in all plans.

In-app monitoring: Create bookmarks and sheets in the monitoring apps that focus on specific consumption areas. Share these bookmarks with space owners or functional teams so they can self-service their consumption monitoring. Inclusive in all plans.

Automations: Build custom workflows that trigger actions based on consumption thresholds, such as sending notifications through Slack, creating tickets in ServiceNow, or disabling specific automations when limits are approached. Value-add feature, if third-party connectors are used.

Setting up each monitoring approach

Creating Data Alerts:

Open the relevant monitoring app (e.g., Automation Analyzer)
Navigate to the sheet containing the metric you want to monitor
Right-click on a chart and select "Alerts" → "Create new alert"
Define the alert condition using an expression (e.g., Sum(AutomationRuns) > 4000)
Set the evaluation frequency (hourly, daily, weekly)
Add recipients (individuals or groups)
Customize the alert message to provide context
Save and enable the alert

Creating Subscriptions:

Open the monitoring app
Navigate to the sheet you want to distribute
Click the subscription icon or access via the context menu
Choose distribution format (image, PDF, or data)
Set the schedule (daily, weekly, monthly)
Select recipients (users or groups)
Add a custom message if desired
Save the subscription

Creating In-App Bookmarks:

Open the monitoring app
Apply filters and selections to focus on specific consumption areas (e.g., filter to a specific space)
Click "Bookmarks" and create a new bookmark
Give it a descriptive name (e.g., "Marketing Space Automation Consumption")
Publish the bookmark to make it available to all app users, and share the link

Creating Automations:

Navigate to Automations in the Analytics activity center
Create a new automation
Use the "Qlik Cloud Services" connector to monitor app data or events
Add conditional logic based on consumption thresholds
Configure actions (send notifications, disable automations, create records)
Test and enable the automation

All of these tools support distribution to groups, making it easy to ensure the right teams have visibility into the consumption metrics relevant to them. Space administrators can receive alerts about their space consumption, development teams can get daily subscription reports, and executive stakeholders can receive monthly summary reports.

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:

Create a sheet showing: Weekly peak trend (last 8 weeks), Top 10 apps by data volume, Space breakdown
Create a subscription
Schedule: Monday at 9:00 AM
Recipients: Administrators, managers
Format: PDF
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:

Trigger: Scheduled monthly on the first weekday at 9:00 AM
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
Block 2: Generate a snapshot from Automation Analyzer using the Qlik Reporting connector:
- Top 10 consuming automations
- Executor breakdown
- Space breakdown
Block 3: Generate snapshot from Reload Analyzer using the Qlik Reporting connector:
- Top 10 apps by reload duration
- Reload frequency analysis
- Failed reload summary
Block 4: Compile snapshots into a single PDF or PowerPoint
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:

Qlik Community Official Support Articles:

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.

article How to take control of your Qlik Cloud subscription: a guide to monitoring and managing consumption in Official Support Articles

How to take control of your Qlik Cloud subscription: a guide to monitoring and managing consumption

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

Example 1: Third-party automation runs monitoring and alerts

Example 2: Data for Analysis capacity monitoring

Example 3: Comprehensive monthly consumption review package

Your action plan: From reactive to proactive

Additional resources