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.
I agree with this suggestion.
Being able to set cost anomaly alerts based on both $ thresholds AND % thresholds will prevent many false positives. (Many smaller accounts will trigger a % change increase but be minuscule in actual $ change. Many larger accounts will trigger a $ change but might actually be a small - and expected - change % wise.)
It is common to use both measures in conjunction to determine whether a cost change requires a response.
Currently, the Cloudability cost anatomy toll allows the user to set an alert threshold on $ change OR % change and not both.
The cost anomaly function in AWS gives the user the ability to set both $ thresholds and % thresholds. But it also gives the user the ability to determine if the anomaly alert will be triggered when either threshold is crossed (OR) or both thresholds are triggered (AND). See the attached screenshot showing this option in AWS.