Skip to Main Content

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Not under consideration
Created by Guest
Created on May 19, 2021

To expand API for MQ or the messaging REST API

To expand API for MQ or the messaging REST API to include functionality to allow for getting IBM MQ accounting / statistics / event / audit messages from their various queues, formatting them, and then returning them as a JSON . This would allow for a previously impossible level of integration out of the box with products like Elastic, Splunk, Prometheus, etc. Given that IBM has already built a JSON MQSC REST API endpoint, it would be good to expand the REST interface to include more sophisticated monitoring capabilities.

Idea priority Medium
RFE ID 150577
RFE Product IBM MQ
  • Admin
    Mark Taylor
    Nov 24, 2021

    See for an example of how to combine the event formatter with the REST API

  • Guest
    Jul 14, 2021

    Essentially, the goal of this idea is to have the data mentioned be available in JSON format without having to build or purchase an external utility to do the parsing for us. The mechanism through which this is achieved is less important and I'm open to other suggestions. But competing products such as RabbitMQ are already far better placed in this regard than IBM MQ is.

  • Guest
    Jul 14, 2021

    Hi Mark,

    As the original person that had this idea submitted via our IBM AVL, one of the reasons we do not have sophisticated monitoring of MQ in here at the moment is that PCF is a royal pain to deal with. It's not standardised whatsoever, so whenever IBM adds new stuff, you have to build a whole new parser or extend the existing parser to deal with the new functionality.

    PCF is a legacy standard that predates XML and JSON. It is understandable if IBM can't get rid of it due to backwards compatibility concerns, but to meet IBM's goals of cloud native products, abstracting PCF away and exposing everything as JSON is far more suited to a cloud native environment.

    Regarding the qm.ini switch for outputting QM logs as JSON, I'd love to see something similar for the accounting / statistics / event messages. That way backwards compatibility is preserved, while also allowing for the product to more easily integrate into a cloud environment.

  • Guest
    Jul 13, 2021

    Hi Mark:

    Applying an outside MQ solution to an inside problem compounds the effort, as well as increasing the number of moving parts. By setting a qm.ini switch, MQ already can create logs in JSON. This would be a logical extension of that same facility.

  • Admin
    Mark Taylor
    Jul 13, 2021

    It is not likely that we would put a PCF formatter into the MQ REST messaging interface. Instead, you should look at the amqsevt sample program which converts these events into JSON - that data can then be read in a variety of ways including using programs like amqsput to put text formatted messages back to a queue, from where they CAN be read by the REST interface.

  • Guest
    Jun 4, 2021

    Excellent idea.