Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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.

Categories Other
Created by Guest
Created on Aug 27, 2024

Containers should support logging to filesystem, console, or both.

Our containers need to be configurable via helm to log to either a persistent volume, the console, or both. A lot of our containers today support either console or persistent volume but do not allow both at the same time.

What is your industry? Computer Services
How will this idea be used?

Logging to console is important so logs can be seen in the OCP or K8s UI and more importantly be forwarded to log aggregators like Elasticsearch or Splunk.


Logging to persistent volume is important for customers who do not have a log aggregator so need the logs persisteted in a volume. Otherwise the logs disappear if the container crashes or restarts.


Logging to both has been requested by a few customers. In some cases they still want to be able to view logs from the console for day to day operations, but also want access to logs on the filesystem for history (because they have no aggregator) or because it's much easier to send the log files to support vs trying to extract logs from an aggregator.