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

Provide logging to stdout\stderr for MFT redistributable package

For containerised environments with a centralised logging mechanism there is often a requirement to direct log output to stdout\stderr of the pid=1.

The log to file options currently provided by MFT include logic to rotate based on size\age which makes it impossible to 'redirect' the files.

Case TS005617616.

Idea priority Medium
RFE ID 150771
RFE URL
RFE Product IBM MQ
  • Admin
    Mark Taylor
    Reply
    |
    Aug 24, 2021

    The comments here describe what is already available, which is at least a partial solution to the requirement. There are no current plans to do anything further in this area

  • Guest
    Reply
    |
    Jun 21, 2021

    private
    Thank you.

    As of now contents of output0.log and pcevent0.log are displayed on the console. Contents of capture0.log are not displayed on console.

    You may also want to have a look at MFT Container image published in DockerHub at https://hub.docker.com/r/ibmcom/mqmft.

    Thank you

  • Guest
    Reply
    |
    Jun 18, 2021

    Thanks, this sounds promising. I'm assuming this will also include the capture0.log (which we enable). How about the stdout\stderr files, will they also output to console? I will test this and update this RFE with my findings.

  • Guest
    Reply
    |
    Jun 17, 2021

    private

    Hello,
    Further update: Using -F with fteStartAgent command, events that were written pcevent0,log file, are output console. So you have both output0.log and pcevent0.log events displayed on the console.

    Hope this helps.
    Thank you

  • Guest
    Reply
    |
    Jun 17, 2021

    private

    Hello,

    By default agent runs as daemon. However there is a documented option, -F to run agent in foreground. This option can be specified when starting an agent using fteStartAgent command, for example fteStartAgent -F . Option is case sensitive, so you must use upper case 'F'. When running in foreground agent outputs messages to console. This includes the event messages logged to agent's output0.log file.

    Could you please look at using the 'F' opion and see if that helps? Yes, it does not display contents of other log files like pcevent.log etc. I think you would be mostly interested in events logged to agent's output0.log file.

    Thank you.