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 Under review
Created by Guest
Created on May 3, 2024

Metric anomaly detection for subset of alerts based on user-defined rules

In CP4AIOps 4.3, we introduced the ability to measure the number of events coming through the system and then send them to Metrics to determine when event volumes change significantly. The number of events coming through the system is defined as alertGroup in the metric search UI, but this may be too broad across all alerts to generate impactful anomalies. The user should be able to define additional alert groups for certain categories (e.g. e.g. by location, by datacenter, application, etc.) where it would make sense to run metric anomaly detection. 

Bank of America wanted us to consider the following use case: "For example: What if we normally get a memory alert once a month and then all of a sudden we get a memory alert 4 times in a day?" In order to identify these patterns, we might first have to create an alert group based on rules like "includes the string 'memory alert' in alert description field" and "alerts must be coming from the same resource group. The ability to define an alert group like this would have to be defined in the UI like the way scope-based rules are defined.

Idea priority Medium