IBM Data Platform Ideas Portal for Customers
Hide about this portal


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Future consideration
Workspace Cloud Pak for Data
Components Cloud Pak for Data Platform
Created by Guest
Created on Jun 27, 2025

RELATED IDEAS

DEBUG Level logging support across all Cloud Pak for Data services

See this idea on ideas.ibm.com

At this time we have not standardized the implementation of DEBUG level logging for all CP4D services. Some services support enabling DEBUG level logging but that needs to be done manually through the deployment, ie. "oc edit deployment <deployment_name> and others do not support any DEBUG level logging altogether.

Ideally we should make it mandatory that all CP4D services support DEBUG level logging as part of the Operand (CR) the way we support Deployment Resource changes. 

In the example below, end users should be able to simply run an Operand patch command which identifies the Deployment and level of logging, this parameter by default (when not set) would be info for informational messages only .

oc patch <CR_KIND> <CR> { "op": "replace", "path": "/spec/custom_resource", "value": { "<deployment_name>": { "LOGLEVEL": "debug", }} }

Needed By Not sure -- Just thought it was cool
  • Admin
    Narayan Samal
    Jul 18, 2025

    Thank you for sharing this idea. We appreciate your input and will review this as part of our 2026 planning cycle.

    Reply
  • Guest
    Jun 27, 2025

    Some pods might not have this support at all, so customers should have the ability to control the logging Especially if they have long running jobs that runs for 365 around the year like Dataservice jobs

    Reply
  • Guest
    Jun 27, 2025

    DEBUL levels should be dynamically settable without having to restart pods, for that there would need to be iether a polling mechanisms or a push notification mechanism to re-load the logging configuration.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.