Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Mar 26, 2018

RELATED IDEAS

MQ Application Activity Trace - Filtering by Queue Name

RFE 55753 allows additional options for controlling the activity events produced. However, while mentioned, tracking by queue was not part of the implementation. Filtering by specific queue name is vital to any production tracing environment.

In this case, other trace events which may not be known can be omitted. That is, when tracing by queue, only events between MQopen and MQclose for that queue are required. For example, MQConnect is not relevant to this request nor requests to other queues. The key business objective is to determine who created the message and who read it. As such, it could be implemented as a post collection phase when being written to the buffer for processing, even though at an increase in overhead, some messages would be collected and discarded as not relevant.

The option should be available for both mqat.ini and subscriptions.

Idea priority Medium
RFE ID 118098
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |     Jun 28, 2024

    We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.