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 May 7, 2026

ServiceNow incident integration should supply better metadata for alerts

The x_ibm_waiops_ai_manager_events table that is managed by the ServiceNow incident Integration has only a single field that links the alert to a resource.

This field is called "resource" and it contains the name of the resource.

There are no other fields available to assist in linking these alerts to CIs in ServiceNow.

Suggestions:

  1. Include the uniqueId of the resource
  2. Include a URL linking back to that specific resource (just like the x_ibm_waiops_watson_aiops table has a URL field that links to the incident and the x_ibm_waiops_ai_manager_events has a target_url field that links to the alert)
  3. Allow the user to suggest additional field(s) from resources that should be sent to ServiceNow (as a JSON blob?)
  4. Allow for a field that contains the cmdb_ci.sys_id field (for example if the ServiceNow Topology Observer is active)
  5. Or, even better, have a cmdb_ci Ref field that is an actual link to the CI
  6. Handle composite resources in a useful fashion. Currently only the name of ONE of the resources making up the composite is used, which may not be the name of a CMDB CI in ServiceNow if the resource is a composite even if one of the members of the composite came from ServiceNow.

Handling composites is tricky since even ServiceNow CIs might be merged into a composite, so which sys_id is appropriate. But right now there is not enough information to make anything more than a guess about which CI to link to.

Idea priority Medium
  • Guest
    May 26, 2026

    Also: golden signal and probable cause information including ranking would be useful.