Skip to Main Content

This is an IBM Automation portal for Integration products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Future consideration
Created by Guest
Created on Apr 16, 2019

Provide more detailed information on wait times incurred when using the HA and/or DR features of the MQ Appliance

Today there is no way to tell whether network latency or other delays on the HA and/or DR interfaces are impacting the performance of queue managers making use of either or both of these features on the MQ Appliance. Excessive delays when using either or both of these features can only be inferred by using tools such as DPMON and looking at DISKBUSY time. But if DISKBUSY time is high, there is no way to tell if the busy-ness is due to writes to the local SSDs, the HA replication (if in use) and/or the DR replication (if in use). If excessive delays are seen it requires much effort to determine exactly which disk writes (local, HA or DR) are seeing the most delay. This is particularly important when DR replication is in use, since by definition this replication will be performed over a non-trivial network and distance. Being able to determine what is contributing to high DISKBUSY times in the MQ Appliance will allow slowdowns in MQ throughput due to external causes to be identified and resolved more quickly. And ideally, this information will be reported via the $SYS system topics, so we will not have to depend on service tools like DPMON to monitor this. This is especially useful when a high percentage of the traffic is NOT Persistent and might not be reflected in Log write times. Also would be very useful for predictive capacity planning.

Idea priority High
RFE ID 132111
RFE Product IBM MQ
  • Guest
    Jul 23, 2019

    Adding more statistics is a reasonable requirement and will be considered for future versions of the appliance firmware.


Provide statistics on the HA and DR replication interfaces to help identify delays in message throughput on the MQ Appliance

Today there is no way to tell whether poor MQ messaging throughput on the MQ Appliance is due to network latency or other delays on the HA and/or DR interfaces. It would be immensely helpful if it were possible to gain some insight into delays tha...
over 5 years ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration