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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
See https://marketaylor.synology.me/?p=959 for an example of how to combine the event formatter with the REST API
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.
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.
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.
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.
Excellent idea.