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 Jan 15, 2024

MQ IPT Logging enhancements

Request to upgrade the connection logging in MQ IPT in order to make logs valuable and serchable for Splunk.
logging tools like Splunk prefers to have Key=Value pairs for values in order to index an entry/event
Key=Value pairs makes it possible to search for all that has happened to a route/port.


But IBM MQ IPT logs like this:

Sun Jan 14 05:53:57 CET 2024 conn nodata aaa.bbb.ccc(9482) OK       4125-2
Sun Jan 14 05:53:57 CET 2024 conn accept         OK       5025-1

Which makes it impossible to know in Splunk what is source and what is destination.

I wish for following (or similar) syntax:

mqipt_datetime="2024-01-14T05:53:57.00" mqipt_msgid="MQCPIxxx" mqipt_type="conn" mqipt_event="nodata" mqipt_source="nodata aaa.bbb.ccc" mqipt_sourceport="9482" mqipt_dest="" mqipt_destport="4125" mqipt_compl="OK" mqipt_thread="4125-2" mqipt_message=""

mqipt_datetime="2024-01-10T15:07:00.00" mqipt_msgid="MQCPIxxx" mqipt_type=conn" mqipt_event="close"  mqipt_source="" mqipt_sourceport="4138"  mqipt_dest="" mqipt_destport="7000" mqipt_compl="ERROR" mqipt_thread="7000-0" mqipt_message="Unrecognized SSL handshake request '54'"

Maybe include option to have log in JSON format like the mq error log
Maybe also include routename in log entries.

Also update console.log similar and with timestamp




Idea priority High
  • Admin
    Mark Taylor
    Mar 28, 2024

    This is something we'd like to do in a future version of IPT