Skip to main content Skip to complementary content

Monitoring capacity usage by executions with detailed consumption reports

Last updated: 9/3/2026

With the Data Capacity Reporting App in Qlik Cloud, you can monitor capacity consumption by Job executions in Talend Management Console.

The feature provides insights into the total resource usage of your Talend Management Console accounts or tenants. It measures current and historical monthly capacity usage by the number and duration of executions across all environments, including development, testing, and production.

Prerequisites:

  • You must meet all the requirements listed in this Prerequisites section.
  • Configure Qlik Cloud and Talend Management Console. See this section for instructions and the complete list of prerequisites.
  • Distribute the reporting app to ensure it contains up-to-date consumption data.

The Qlik Cloud administrator distributes the Data Capacity Reporting App from the Settings page in Qlik Cloud, making it available in their personal space and sharing it with report users. To include the latest information, the administrator must regularly regenerate and share the app.

By distributing the app, the administrator generates a consumption report in their personal space.

Job executions

Job executions refer to Job task runs in Talend Management Console.

The Job Executions page presents your current month's usage of the capacity, an overview of historical usage of the last 12 months, and detailed usage of up to the last 3 months.

Only started executions are taken into account for this measurement. For batch Jobs (non-streaming), an execution that fails to deploy does not count. For streaming Jobs (always-on Jobs including Routes, Data Services, and Spark streaming Jobs), all started executions are counted. For the started executions, those with the Failed status (DEPLOY_FAILED and EXECUTION_FAILED in API responses) are excluded from the measurement for batch Jobs, thus consuming none of your capacity. For streaming Jobs, failed executions are always taken into account.

Information noteTip: For batch executions, those with the Terminated status (EXECUTION_TERMINATED) are excluded from measurement up to a duration threshold. For more information, see Duration ratio.
  • Usage overview:

    The bar charts provide a consolidated overview of all your tenants, without the option to filter them by individual tenants.

    As indicated in the legend of the charts, the dotted line represents the maximum capacity you expected to consume, and any part of the bar that exceeds this line turns red.

    The bar charts of a consolidated view of Job executions.
  • Detailed view:

    For detailed usage, you can filter information by months, tenants, environments, spaces, and engines.

    The detailed view of the capacity usage.

Job duration

Job duration refers to the execution time of a Job task in Talend Management Console.

Along with Job executions, the total duration of your Job executions also serves as a value meter to measure your monthly capacity consumption.

The view of the Job duration metrics has the same layout, filters, and timeframe limitations as the Job Executions view, with the following characteristics:
  • The failed executions of non-streaming Jobs (also referred to as batch Jobs) are excluded from the measurement. Streaming Jobs (also referred to as always-on Jobs) including Routes, Data Services, and Spark streaming Jobs, are always taken into account. A failed streaming Job task is considered to be completed.
  • For Terminated (EXECUTION_TERMINATED) executions of batch Jobs, the duration is excluded from the measurement but is subject to a reasonable-use limit.

    The total duration from Terminated batch executions must not exceed a reasonable percentage of the total batch chargeable duration, calculated as follows:

    EXECUTION_TERMINATED / (EXECUTION_SUCCESS + EXECUTION_REJECTED)

  • For streaming Jobs, the duration is measured in hours starting from the Start Execution time and accounted for in each of the months 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 in a month, a 5% conversion rate is applied, resulting in 1,200 effective chargeable hours.
    • For any remaining hours beyond 24,000 in a month, a 1% conversion rate is applied.
    For example, a user with streaming Jobs that ran for 43,000 actual hours in a month is only charged for 1,390 hours towards their capacity plan.
    Calculate chargeable hours
    Actual hours Conversion rate Chargeable hours Effective conversion rate
    24,000 5.00% 1,200 5.00%
    19,000 1.00% 190 1.00%
    Total: 43,000 N/A 1,390 3.23%
The Job duration view to measure capacity consumption

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!