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).
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.
The formulation of the request look potentially slightly misleading to me. I think it is not necessarily about selecting the same metric twice, but instead setting separate thresholds for a single metric with for one each severity level. Furthermore, the example states a two-sided range for the WARN severity, while a once-sided range for the CRITICAL severity, using a mix of threshold operators.
Personally, I think the same thing can be specified a little simpler, such as:
Metric: CPU usage
Threshold Operator: >=
WARN Threshold: 80%
CRITICAL Threshold: 90%
In a brief, this defines an "escalation plan" that an Issue is triggered once the threshold reaches 80%. Which escalates to a CRITICAL once it reaches 90% during the lifetime of the event.
Such a behavior is already present for a handful of Instana's built-in events. Just not yet for any of the Custom Events or Smart Alerts.
State of Missouri has been demanding this feature for over a year. If we can fast track this feature that would be instrumental to our growth.