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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Just for completeness, this is a follow-up of https://automation-management.ideas.ibm.com/ideas/INSTANA-I-1773. And it was identified as a nice-to-have, but not an ITM blocker, due to the existing workaround of creating creating 2 alert-configurations with different thresholds/severities.
In contrast to what is described in the Idea description, there is hower one thing that is different. We don't allow defining a range (e.g. WARN from 80%-90%), and we also don't intend to do it that way. Instead, we intend to define an escalation, of different thresholds all using the same threshold operator, to ensure there are no gaps/conflicts in the threshold, when then cause the described problems in the Idea description.
> And, the original Event MAY close depending on the grace period
This would therefore not happen, neither in the current (workaround) solution of 2 Cutom Events, because the rule would not be defined as WARNING in range of 80-90%, but WARNING > 80%, which would be still the case when the metric changed to 92%. Both defined Custom Events (WARN if > 80%; CRITICAL if > 90%) would be active at that time, as both conditions are met.