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 Not under consideration
Created by Guest
Created on Aug 7, 2020

MQ Support for Distributed Tracing

Existing Application Performance Management (APM) tools, and emerging W3C standards for Distributed Tracing require propagation of tracking meta data across application protocols.

For applications using HTTP as the communication protocol between application components, this meta data can be placed in HTTP headers to be accessed by downstream APM agents or tracers while not fundamentally impacting the application being monitored.

For applications that use messaging protocols for communication between application components, the propagation of tracking meta data is typically handled by adding the meta data in message properties.

For IBM MQ based applications, the insertion of unexpected message properties can cause the underlying application to fail. While is it possible to change the application to handle these additional properties, it is often not technically or financially feasible to do so.

Ideally there would be a mechanism to propagate distributed tracing meta data across IBM MQ messages without requiring application or MQ configuration changes.

Idea priority High
RFE ID 144500
RFE Product IBM MQ
  • Admin
    Matthew Leming
    May 24, 2022

    Moving as not under consideration. This idea no longer matches our current priorities, and is unlikely to be done in the next couple of years.

  • Guest
    Sep 16, 2020

    We are considering adding support for this to a future version of MQ

  • Guest
    Aug 9, 2020

    To avoid message properties being given to an MQ application that does not understand them, define the queue with PROPCTL(NONE)