Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 (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.

Add a new idea Subscribe
Status Under review
Workspace IBM Cloud Pak for AIOps
Created by Guest
Created on Jun 24, 2026

RELATED IDEAS

Intelligent handling of "flapping" alarms

Objective: Prevent flapping alerts (Alarm, OK, Alarm, OK, ...) from flooding the queue with duplicate incidents by utilizing historical pattern matching and rolling-window suppression.

  • Pattern Detection: CP4AIOPS should analyze historical data and seasonality to identify and "memorize" flapping alert behaviors.
     
  • Incident Suppression: Once a flapping pattern is recognized, future occurrences should be filtered out to prevent the creation of many individual incidents.
     
  • Rolling-Window Handling: Instead of separate tickets, route these alerts into a single, continuous incident using a rolling time window. This incident will remain open until the underlying issue is fully resolved.
     
  • First-Time Trigger Logic: When a recurring alert is identified against historical data, the system should automatically activate X-in-Y suppression (hold-off) and transition the alerts into the rolling-window incident model.
Idea priority Medium

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.