Cloud 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
We have a real production use case supporting this idea.
We need to alert on sustained memory usage above 80% (warning) and 90% (critical)
on our servers. When this condition remains active for an extended period
(e.g., 24+ hours), our client requires periodic reminder notifications — for
example, every 1 hour — for as long as the event stays open, in addition to
the initial notification.
Currently there is no native way to do this without artificially closing and
reopening the event, which would corrupt the event's real duration/history
and break correlation with the underlying issue.
A configurable resend interval (per alert, or at minimum per alert channel)
would let us keep the event lifecycle intact while still ensuring the team
doesn't lose track of long-running critical issues. This is standard
functionality in other observability tools (e.g., Datadog's renotify_interval,
Zabbix's escalation steps, ManageEngine OpManager's Recurring Trigger), so we'd
consider this a gap relative to competing products.
Voting and adding our use case in support of prioritizing this.