Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under consideration
Components Q Replication for Z
Created by Guest
Created on Apr 3, 2019

Display of replication throughput per subscription

Today Q Apply stores detailed performance statistics on queue level. This idea raises the request to store certain Q Apply throuput statistics (like rows_processed) on subscription level. Background: Today it is very difficult / sometime impossible to identify the root cause in case Q Apply is overwelmed with workload and in case Q Apply cannot guarantee the required latency. In these situations we would like to know which tables are effected (to take correctve action on the source). The performance details we ask for could for example list the x heaviest hitters (e.g., the 10 subscriptions with the most workload). Ideally this information would be stored in a statistics table periodically or at least be written to a log file for investigation.