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 Under review
Created by Guest
Created on Jan 20, 2026

Provide a field mapping in Incident Schema for enriching distinct list of domains from associated alerts.

Domain is not a default column defined in Netcool/AIOps Schema, but is widely used to recognize which Telecomm Network it belongs to say IP, Transport, Mobile etc. 

Incidents can be of with single domain correlated alerts or with multi domain correlated alert. In order for easier identification, there is a need of unique identification column with distinct list of domains associated with alert in Incident schema which can be added in Incident Viewer.

If we wanted to identify which all domain alerts are associated to an incident from the Incident Viewer, separate column needs to be enriched with unique list of domains fetched from all associated alerts. This will help in easy identification of cross domain correlation, quick understanding of impacted services from the Incident Viewer. This also helps in creating specific filter conditions and views restricted to different domain owners saving the time to navigate through each and every incident.

 The domains obtained from alert can be of single or multiple. If multiple, it should be listed in comma separated format under a column in Incident Schema.

As the schema can vary across customers, it could be better to provide a provision to define a NetworkDomain field in Incident schema which should get the   dynamic distinct list of associated domain values once Incident is triggered.  There should be an option provided to user to define Network Domain field mapping during Incident Creation. Let's say, for user 1 domain associated with the alert is enriched in 'alert.Domain' field and the user2 is using alert.SrcDomain, so by providing provision for mapping the domain to a specific field in Incident schema this solution can be made dynamic enough to accommodate any field of Domain mapping. 

Once mapping is confirmed, the logic should iterate through the complete alerts in Incident and fetch the distinct value from domain field and enrich NetworkDomain field in Incident Schema.

The field should get auto updated in case any new domains are added in the group which are not in previous list.

 

 

 

 

Idea priority High