Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps 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.

Status Submitted
Workspace Instana
Categories MQ
Created by Guest
Created on Jul 17, 2024

Improve tracing visibility

Hello,

I tried to install UserTracing exit on MQ 9.4.0.0 on linux. Here after is my data chain :

MQ 9.4.0.0 -> UserTracing exit -> otelcol -> jaeger backend ->grafana

It works, and gives tracing times, but unfortunately, it's not as advanced as I expected...

 

The put time is traced well (some microsecs), but the get record takes into account the queue time and not only the get time...

So you are not able to distinguish an asynchronous get which is getting well (some microsecs) after a lying queue time of 10sec for example, from a get that is not getting well with maybe uncommited message etc...

 

I would have expect 3 record sections (PUT  -> QTIME -> GET) instead of 2 (PUT  -> GET).

Idea priority Low