Skip to Main Content
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.

Status Submitted
Created by Guest
Created on Dec 3, 2025

Remove deleted topology group references from alerts.

We have come across the scenario where alerts are having references of topology groups which are deleted or not active in the system. This reference has to be removed from alerts or mark the topology group as deleted when they are inactive. The probable cause ranking pods often check the topology relationship of alerts based on the topology groups and ends up in continuously querying for missing topology groups as in a loop. If properly marked as deleted, probable cause pods or any dependent pods can avoid processing of the deleted topology groups and avoid errors.

If any topology template is not active or has been deleted from system, the alert metadata has to be updated with the topology group as deleted or remove the reference.

There are chances we will be dismantling the groups, and if alert still holds the references, it will often create issues on other dependent pods who relay of alerts like Incidents, Topology, Probable cause ranking etc.

Idea priority High