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 Oct 1, 2024

Train events to identify event anomalies

Events are received continuously and have a corresponding/expected payload which is used to perform important backend processing, e.g. policies will trigger incident creation based on field values, events are grouped based on scope values settings, events are associated to topology resources based on their matchToken values. If  event data sources like a SCOM or Zabbix system will change the payload due to updates or config changes, the backend processing might stop to work. If the events would be trained, AiOps would know how typical events will look like (field value settings) and can detect anomalies if a value does change suddenly, a field becomes empty which is wasn't before or is completly missing in the payload. Detecting these kind of deviations are hard to be executed by an human being but AI can easily learn the "normal" event payload (baseline) and detect anomalies if events start to look different than before.

Idea priority Urgent