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 Functionality already exists
Created by Guest
Created on Sep 1, 2021

Support for Kubernetes log outputs

From CP4I 2020.4.1 onwards, Cloud Pak logging is now integrated with OpenShift cluster logging running on EFK. Fluentd is able to consume logs that adhere to the kubernetes native log outputs making log integration seamless.

Support for kubernetes native log outputs like stderr and stdout is highly desirable for MQ native logging e.g. the AMQ* logs.

Idea priority High
  • Admin
    Mark Taylor
    Dec 14, 2021

    The MQ Operator already supports JSON logging. You just need OpenShift Container Platform 4.8 for the version of OpenShift Logging which can handle JSON logs.

  • Guest
    Oct 5, 2021

    I have managed to get JSON log format working with OpenShift Container Platform 4.7 cluster logging. Look forward to the new MQ JSON logging in OpenShift Container Platform 4.8.

  • Admin
    Mark Taylor
    Oct 5, 2021

    The MQ containers already output error logs on stderr, so we think that more information is needed on what exactly this request is looking for

    1. Getting the full MQ error log on stderr. Currently, the container either outputs the JSON error log line, or, if basic formatting is requested (the default), just the log message line.

    2. Getting the web server logs onto stderr. This is already possible by setting some environment variables, but configuration could perhaps be simplified

    3. Changing the text-based format of the logs to conform with the format used by other Kubernetes components, so that the same parser can process all messages. We are unlikely to do this, as the Kubernetes format is:

      1. Specific to Kubernetes in some ways, for example the inclusion of a source file name in the output

      2. Uses declarative logging, rather than messages with inserts. MQ uses messages with inserts.

    For (3) the advice would be that from OpenShift Container Platform 4.8 onwards, JSON logging is supported again, so enabling MQ JSON logging (using ".spec.logFormat: JSON") would give fully structured logs.