Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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.

Add a new idea Subscribe
Status Planned for future release
Workspace Instana
Categories MQ
Created by Guest
Created on Jun 5, 2026

RELATED IDEAS

Need better handling of mistakes in the mqtracingexit.conf file for MQ tracing

Minor syntax errors within the mqtracingexit.conf file cause the MQ Tracing to file.  There appears to be sensitivity to whether or not there are spaces between the parameters, the equal sign, and the value.

This is related to support case TS022198476

For example, the default config file might have a parameter like this:

OTLP_EXPORTER_HTTP_URL = "http://localhost:4318/v1/traces" 

But the customer specified this:

OTLP_EXPORTER_HTTP_URL="http://localhost:4318/v1/traces" 

There were other minor syntax differences, so it is possible there are other issues within the configuration file.

We are asking for 2 things with this idea.  

  • First, the code should be more forgiving about handling minor differences in spacing.  For example, a customer should be allowed to have zero spaces, 1 space, or even 2 spaces between the parameter name, the equal sign, and the value.  
  • Second, when there is a syntax error, there should be an obvious error message in the MQ logs indicating what went wrong.   The current behavior is that transactions are not traced, but there is no reason why.
Idea priority High

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.