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 12, 2025

Modify the time span between alert clearance and alert deletion and trigger policy when an alert is deleted

Background

In the current IBM AIOps , alerts that reach the cleared state are automatically deleted after approximately 2 minutes.
While this default behavior helps optimize database performance, it lacks flexibility for environments that require longer retention periods or additional post-clearance processing.

During migration from legacy Netcool/OMNIbus environments, this limitation becomes significant, as administrators often rely on configurable clearance retention periods and triggers that perform cleanup or notification actions before alerts are permanently deleted.

Problem Statement

  1. The time span between alert clearance and deletion is fixed to 2 minutes and cannot currently be modified.
    1. Some environments require a longer delay to allow for post-processing, reporting, or synchronization with external systems.
  2. There is no mechanism to trigger a policy when an alert is deleted, which prevents automation of cleanup tasks or post-deletion actions (e.g., notifying downstream systems, updating audit logs, or adjusting correlated entities).

Proposed Enhancements

  1. Configurable Alert Deletion Delay
  2. Policy Trigger on Alert Deletion
Idea priority Urgent