Skip to Main Content
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
  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 Future consideration
Created by Guest
Created on Nov 23, 2016

Queue Manager Errors Written to Topic

Please enhance MQ to publish its messages that it writes to the error logs (e.g. MQP1MSTR/MQP1CHIN job logs, distributed queue manager error logs, distributed FDC errors) to also a system topic. This would allow remote monitoring applications to be able to subscribe to this topic and consume these error messages.

A scaled down and summarized message would be more suitable for something large like a distributed FDC or a z/OS CSQSNAP. Basically, if the error consitutes a lot of data, keep the published version short and sweet.

Idea priority High
RFE ID 97700
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Dec 19, 2016

    We have published various articles on how the MQ error logs can be monitored using a variety of tools. See for example

    https://www.ibm.com/developerworks/community/blogs/messaging/entry/Sending_MQ_logs_to_the_Bluemix_Logmet_service?lang=en
    https://www.ibm.com/developerworks/community/blogs/messaging/entry/mq_aws_cloudwatch_logs?lang=en
    https://www.ibm.com/developerworks/community/blogs/messaging/entry/Storing_and_searching_MQ_logs_in_Elasticsearch?lang=en

    These give opportunities for long-term storage and searching of this activity.

    We are considering various rationalisations of error log and event generation for the future, which could include turning some of the activity into publications, but the type of content for each is very different (error log is highly text-based, events not so much)

  • Guest
    Reply
    |
    Dec 6, 2016

    Hi,
    Good idea, just why not generate an event message for it? The today can already process monitors and the redirect into a topic is also no problem.
    regards
    detlef