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 Apr 26, 2024

Existing Incident Correlation in Customer ITSM with AIOps Generated Alerts

In some customer environments, application end users may create tickets in their ITSM portals along with any other monitoring system alerts. This creates additional noise and overhead for the operational teams to investigate and link to another known-incident. This is often related to an existing failure that the Cloud Pak for AIOps has detected, or AIOps would eventually detect an issue related to the same root cause as the user's experience.

This idea is about correlating existing incidents (user or existing monitoring system generated) in the ITSM tool with incoming alerts into CP4AIOps so that we can determine if an existing incident in the ITSM tool should be used as the parent incident or if AIOps should create a new ticket in the ITSM tool.

In a customer example, both the monitoring systems and users are creating tickets. User creates a ticket because they have had a bad experience with their system failing, reports not run or even as drastic as an order management system not generating order forms for the goods drivers to leave a warehouse with products. At the same time, monitoring systems are flagging issues and tickets into the ITSM tool but with no correlation or grouping.

Ultimately, the goal is to show value through how we can reduce the need for users to create tickets at all, by proactively preventing the monitoring incidents before the user experiences anything at all, but this is not the case for a lot of use cases.

Idea priority Low