Understanding the subscription value meters
Value meters determine pricing and billing for Qlik Cloud subscriptions by measuring resource usage. Capacity-based subscriptions primarily use data volume, but the specific value meters depend on your subscription type.
The following table shows the primary value meters for each subscription type:
| Subscription option | Value meters |
|---|---|
| Qlik Cloud Analytics Starter | Users |
| Qlik Cloud Analytics Standard | Data for Analysis |
| Qlik Cloud Analytics Premium | Data for Analysis |
| Qlik Cloud Enterprise | Data for Analysis, Data Moved |
| Qlik Talend Cloud Starter | Data Moved |
| Qlik Talend Cloud Standard | Data Moved |
| Qlik Talend Cloud Premium | Data Moved, Third party data transformations ($/GB), Job execution, Job duration |
| Qlik Talend Cloud Enterprise |
Data Moved, Third party data transformations ($/GB), Job execution, Job duration |
| Qlik Anonymous Access | Anonymous Capacity, Anonymous Concurrent Sessions |
Monitoring resource usage
Administrators can track usage of Data for Analysis, Data Moved, and other resources in the Administration activity center and the Data Capacity Reporting App.
The service account owner (SAO) can monitor consumption and view subscription details in My Qlik.
For more information, see:
For more information about the license metrics, see the Qlik Cloud® Subscriptions product description.
Data for Analysis
Qlik Cloud Analytics is measured on Data for Analysis volume. This value meter counts the total volume of data loaded into and analyzed in Qlik Cloud. Your monthly peak usage is compared against your purchased capacity. Exceeding your capacity may incur overages.
For detailed information on what data is included, how usage is calculated, and best practices for managing your data, see Data for Analysis.
Data Moved
The Data Moved metric is the sum of all data moved to a target. You can move data to any type of target. The type of sources you can move data from depends on your subscription. There is no limit on the number of targets or sources.
Data Moved is measured from the beginning of the month. It is counted as it is landed on the target. This means that the same data replicated to two different targets is counted twice. The initial full load of new tables or files is free and is not counted.
The Data Moved volume is calculated as the number of rows in the dataset multiplied by the estimated row size. The estimated row size is calculated as the total size of all the columns in a row, based on the data type of each column. For details on how the internal representation of the data types maps to your target schema, see Connecting to cloud data platforms in your data projects and go to the Data types section in the topic for your cloud data platform.
The row count used in the calculation of the Data Moved volume might differ slightly from the expected value. These small differences are expected and caused by technical artifacts that cannot be controlled by Qlik.
For example, when loading a big table, the database might send the same row twice (phantom reads) or count a row both as reload and as a change row. Differences might also arise in change counts when a change causes a trigger execution, which makes additional unexpected changes, and the change counts are read from a transaction log or a change source.
The Data Moved calculation is based on the landing dataset as it appears in Qlik Cloud. Changes to this dataset will be taken into account, such as adding new columns. If you are trying to reproduce the Data Moved volume calculations, make sure that you are using the right data types as they appear in Qlik Cloud and not the source, as this affects the column size in the calculation. For example, using varchar(20) instead of varchar(10) doubles the column contribution to the estimated row size.
The following table lists the size of each data type. The min() function used for bytes, string, and wstring returns the smallest of the two values, either length/2 or 200.
| Data type | Size (in bytes) |
|---|---|
| Unspecified | 1 |
| BOOLEAN | 1 |
| BYTES(length) | min(length/2, 200) |
| DATE | 4 |
| TIME | 4 |
| DATETIME | 8 |
| INT1 | 1 |
| INT2 | 2 |
| INT4 | 4 |
| INT8 | 8 |
| REAL4 | 2 |
| REAL8 | 4 |
| UINT1 | 1 |
| UINT2 | 2 |
| UINT4 | 4 |
| UINT8 | 8 |
| NUMERIC | 2 |
| STRING(length) | min(length/2, 200) |
| WSTRING(length) | min(length/2, 200) |
| BLOB | 200 |
| CLOB | 200 |
| NCLOB | 200 |
| JSON | 200 |
Example: Calculating Data Moved volume
In this example we have a dataset for product categories. The dataset has 100 rows and the following columns:
| Column name | Data type |
|---|---|
| CategoryID | INT4 |
| CategoryName | WSTRING(15) |
| Description | NCLOB |
| Picture | BLOB |
There is a fixed size for each data type:
| Data type | Size (in bytes) |
|---|---|
| INT4 | 4 |
| WSTRING(15) | min(15/2, 200) = 7.5 |
| NCLOB | 200 |
| BLOB | 200 |
We can now calculate the estimated row size as the sum of the column sizes: 4 + 7.5 + 200 + 200 = 411.5 bytes. Multiplied by 100 rows, this gives us a total data volume of 41,150 bytes.
Third party data transformations
This metric applies to all datasets that are registered using the data task for Registered data. Third party transformations are measured in $/GB from the beginning of the month. GB used for third party data transformations is calculated with the same logic as data moved, that is, the number of rows in the dataset multiplied by the estimated row size. For more information about how to calculate the estimated row size, see Data Moved.
When processing data through the Registered data task, full or initial load processing is counted toward the capacity. Subsequent executions will detect changed rows, and will only count changed records toward capacity.
Job execution and Job duration
Job execution and Job duration are the main metrics for Talend Data Fabric capabilities that are included in Qlik Talend Cloud subscriptions. A job is identified as a distinct Artifact ID as reported in the Talend Management Console.
-
Job executions are the total number of job runs executed and concluded in a given month. Always-On Jobs are counted once in each month the job was running.
-
Job duration means the total duration in minutes, measured from the time a job starts until it stops. For batch jobs, the duration is accounted for in the month the job successfully ended. For Always-On Jobs, duration is measured from the start execution time in each month the job has been running. The actual duration is converted to a chargeable metric using a progressive conversion scale:
- For the first 24,000 hours, a 5% conversion rate is applied.
- For any remaining hours beyond 24,000, a 1% conversion rate is applied.
Full Users
Users with a Full User entitlement can view, edit, and create content in apps, export charts and apps, work with data integration, automations, machine learning, and perform other tasks—provided their user permissions and space permissions allow it. For more information, see Managing user entitlements.
Basic Users
The Basic User entitlement is designed for limited, read-only access. Basic Users cannot create or edit apps and other assets, or work with Data Integration. If granted additional permissions, they are automatically promoted to Full Users. For more information, see Managing user entitlements.
Anonymous Capacity
Anonymous Capacity is only applicable to Qlik Anonymous Access subscriptions. This value meter refers to the total RAM usage that all apps loaded into memory can consume at a given time. This includes tenant user sessions (sessions opened by Full Users and administrators within the tenant) and anonymous user sessions (sessions opened by users who are not logged into the Qlik Cloud tenant).
The Anonymous Capacity of a tenant is defined by the purchased amount purchased within the subscription.
Anonymous Concurrent Sessions
Anonymous Concurrent Sessions is only applicable to Qlik Anonymous Access subscriptions. This value meter defines the maximum number of app sessions that can be run concurrently by anonymous users (users who are not logged into the Qlik Cloud tenant).
The Anonymous Concurrent Sessions of a tenant is defined by the purchased amount purchased within the subscription. You can purchase up to 1000 sessions. For more information, see Qlik Anonymous Access specifications and capacity.