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 Submitted
Created by Guest
Created on Feb 2, 2026

JMS driver/client support logging to java.util.logging

In Kubernetes specifically, the norm is to log to stdout which is supported, but a lot of apps especially using Spring Boot use an internal log4j or logback logging mechanism that conforms to the standards of that company, structure (text/json/etc) as well as location (stdout/file). If the JMS driver logs to java.util.logging then jul-to-slf4j can be used to bridge java.util.logging to slf4j if teams use it and hook into their standard logging. This would be useful not just for Kubernetes but VMs where log ingestion is already setup as it avoids having to setup extra infrastructure to get trace logs, etc. off the servers.

Idea priority High