Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 Not under consideration
Created by Guest
Created on Jan 13, 2023

MCM Cassandra , increase trace retention to 4 days

Our customer from CE needs the retention data of application traces to be 4 days , instead of default 2 days.


We understood this is hardcoded in Cassnadra but can not be changed / configured. 


We are using OCP 4.10.43 + MCM 2.3.28(FP6)



Idea priority High
  • Admin
    Ravikumar Ramachandra
    Feb 10, 2023

    From Engineering Team:

    We appreciate your interest in increasing the trace retention from 2 days to 4 days but we have to advise against this change due to potential storage and performance issues it could create in customer's cp4mcm environment.

    Cassandra is highly performant database but increasing the trace retention would put additional strain on the storage and retrieval of large amounts of data over a longer period of time. This could lead to decreased performance and potentially cause stability issues.

    Our primary aim is ensuring the stability and performance of customer's system, and increasing the trace retention might negatively impact that. Hence declining this request.