Home > Licensing > Monitor capacity consumption

Monitor capacity consumption

Cadence: Daily

Subscription model: All—different value meters apply per subscription

Roles: Tenant Admin (TA), Analytics Admin (AA), Data Admin (DA—Data Moved)

Last verified: 2026-09

Benefits:

• Early warning before capacity limits hit 100% and trigger overage / blocking
• Visibility into Qlik Answers, Qlik Reporting Service, and anonymous-session consumption
• Confirms Data Capacity Reporting App is still reloading

Goal

Notifications appear in the admin console at 80%, 90%, and 100% of any capacity limit (email to the SAO at each threshold). The Home dashboard also surfaces three visual indicators that don't map one-to-one to those percentages: an orange triangle appears as usage approaches the purchased amount, a red triangle once usage has exceeded it, and a red bar during overage consumption. Daily review of the admin console Home dashboard confirms current consumption and provides early warning before limits are reached. The fully Qlik-supported Data Capacity Reporting App provides consolidated capacity consumption reporting on capacity-based tenants and is deployable from the admin console.

Recommended action by threshold

Which meters and editions are hard-capped (no overage). Overage is not enabled for Qlik Cloud Analytics Starter, Qlik Sense Enterprise SaaS (and other user-based analytics), or the analytics capacity included with Qlik Talend Cloud—these block at 100% instead of continuing under overage billing. The indexed pages meter is never overage-eligible on any tier. The overage allowance in the left column applies only to Standard / Premium / Enterprise capacity-based editions, and only to overage-eligible meters. (Per the Qlik Cloud product terms, overage section.)

Reporting Service's 30,000-request-per-day tenant cap and the per-license monthly report cap are hard guardrails (not overage-eligible) and apply on top of the value meters above.

Tasks

Read before acting—gotchas

• Data for Analysis is measured daily but billed on the monthly peak. Each day Qlik measures the size of all resources; the billed figure for the month is the highest day—a high-water mark that doesn't drop until the next month. The daily figure shown on Home and in the consumption app does drop the day after an app is reloaded with smaller data or deleted, but that lower day doesn't undo an earlier peak day, so shrinking an app helps next month's bill, not the current one. Note the trigger is a reload: an app keeps its last-loaded size on the meter every day until it is reloaded, so reducing the source data alone changes nothing. To stop an oversized app from contributing its old size every day, reload it once with an empty load (for example, LOAD * INLINE [Dummy\n0]; as the only statement, or temporarily comment out the script); the next real reload then establishes a fresh, lower daily size. This reset procedure is community-documented, not officially published. (community)
• Reporting Service has a 30,000-request-per-day tenant cap (per reporting-service-specifications-limitations.htm) plus a per-license monthly report cap (varies by Qlik Cloud Analytics edition, per comparing-subscriptions). Both ceilings are actively enforced; plan distribution scheduling against both. (community)
• Word and PowerPoint reports became metered on August 1, 2026. These formats previously did not count against Reporting Service report/request caps; as of that date they're metered the same as other formats, so tenants using Word/PPT distributions will see a step change in reported execution counts. (community)
• Overage notifications are SAO-only and not customizable. 80 % / 90 % / 100 % emails go only to the Service Account Owner; thresholds and recipients can't be changed. Forward via your own monitoring / alerting platform if other roles need visibility. (community)
• Detailed Consumption Report shows file UUIDs only. Map back to filenames via GET /api/v1/data-files/{id} or qlik data-file ls for chargeback / cleanup. (community)
• Data Capacity Reporting App requires daily redistribution, not reload. A reload re-pulls source data into the app; a redistribution republishes the existing app contents to consumers of a managed space without re-pulling data. The Data Capacity Reporting App needs redistribution daily to pick up new tenant consumption, with a once-per-day morning-CET freshness ceiling. Use the Qlik Automate Capacity consumption app deployer template. (community)
• There is no first-party self-service pre-migration sizing tool for Data for Analysis—the Detailed Consumption Report is gated to capacity-based tenants, so user-based customers can't self-serve a figure. To size a move, approximate from the analytics data brought into apps (plus any flat files stored in the environment), or request an exact figure from your Qlik account team, who can provide it for non-QCG customers.

Automation helpers

• Capacity consumption app deployer (Qlik Automate template)—Deploys the Data Capacity Reporting App named in the goal.
• Qlik Cloud Monitoring Apps Deployer—Deploys the analyzer apps that track Reporting Service and other meter sources.

References

• Qlik Cloud capacity-based subscriptions
• Understanding the subscription value meters
• Monitoring resource consumption
• Data Capacity Reporting App on Qlik Help
• Data Capacity Reporting App (Tooling appendix)

Tags: #daily #licensing #capacity #consumption #data_capacity_reporting_app