Cloud Management 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 Submitted
Workspace IBM Cloud Pak for AIOps
Created by Guest
Created on Oct 9, 2025

RELATED IDEAS

Introduce Conditional and Adjacency-Aware Correlation with Path-Based Grouping Feature in AIOps Topology Correlation

The current correlation model in IBM Cloud Pak for AIOps can sometimes over-group alerts by combining all downstream nodes connected to a common parent, even when the parent (anchor) node itself has no alert. This behavior can result in large, noisy alert groups that do not accurately reflect the true fault domain, making root cause analysis more difficult.

Dynamic templates currently treat the parent as “context,” resulting in unioned groups for all connected downstream nodes. Multi-hop and transitive connections further exacerbate over-grouping.

As a Telecomm customer, it is very important to have a grouping with proper identification of Root Cause and ensure no localized faults are missed due to transitive groupings.

Example Scenario:

  • Topology: A → B → C → D

  • Alerts: B, C, and D generate critical alerts, but A (the upstream anchor) has no alert.

  • Current Behavior: The correlation engine groups B, C, and D together in a single group, even though A is healthy.

Impact:

  • Operators see a large, misleading alert group.

  • Overly large groups (100+ alerts) due to union of transitive connections.

  • True root cause (e.g., Node C failure) is obscured.

  • Localized issues related to C; example Node Failure will be unnoticed when the event gets correlated with alerts in B and D.

Proposed Solution:

Introduce Conditional and Adjacency-Aware Correlation with Path-Based Grouping, with the following capabilities:

A. Conditional (Anchor-Based) Correlation

  • Provide option to group downstream alerts only if the anchor (parent) alert is present.

B. Adjacency / Path-Aware Correlation

  • Provide option to correlate only nodes/entities connected through active alert paths.

  • Support multiple alternative paths; any valid path of active alerts is sufficient for correlation.

Example Scenario

Connectivity path is as follows :-

NodeA-->NodeB,NodeC,NodeD,NodeG

NodeB-->NodeE-->NodeF

NodeC-->NodeF

Note :- All grouping should be adhered to existing correlation window logic and should be based on the first occurrence of anchor node alert.

AlarmRaised

ExpectedGroup(Within Defined Correlation Window)

A,B,F

{A,B} SHOULD BE GROUPED AND ALERTS FROM NODEF SHOULD NOT FALL UNDER THE SAME GROUP AS THERE IS NO ACTIVE ALERT IN DIRECT PATH CONNECTING NODEF (WHICH IS ALERT FROM NODEE)

B,C,D

DONOT GROUP, AS TEHRE IS NO DIRECT CONNECTIVITY BETWEEN THEM AND ANCHOR NODE(NODEA) ALERT IS NOT ACTIVE

B,E,F

GROUP THEM TOGETHER AS THERE ARE DIRECT CONNECTIVITY AND ACTIVE ALERT IN PATH

A,C,F

GROUP THEM TOGETHER AS THERE ARE DIRECT CONNECTIVITY AND ACTIVE ALERT IN PATH

A,B,C,D

GROUP THEM TOGETHER AS THERE ARE DIRECT CONNECTIVITY AND ACTIVE ALERT IN PATH

A,E,F

GROUP ALERTS FROM E AND F BUT NOT FROM NODEA AS THERE IS NOT ACTIVE ALERT IN PATH LEADING TO NODEE ( NO ACTIVE ALERT FOR NODEB LEADING THE PATH FROM A-->B-->E-->F)

G,D,A

GROUP THEM TOGETHER AS THERE ARE DIRECT CONNECTIVITY AND ACTIVE ALERT IN PATH

G,D

DONOT GROUP, AS TEHRE IS NO DIRECT CONNECTIVITY BETWEEN THEM AND ANCHOR NODE(NODEA) ALERT IS NOT ACTIVE
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.