About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Customer want to add a feature in Cloudability that will track changes in system configurations (such as billing system updates, infrastructure changes, or settings modifications) and display them in anomaly reports.
This means that when Cloudability detects a cost or usage anomaly, users will be able to see if any recent system changes happened around the same time, helping them quickly figure out if the change caused the anomaly or if something unexpected happened.ˀ̉
Currently, when there’s a sudden cost spike or an unexpected drop in usage, teams have to manually investigate:
Were any settings changed? Was there a new policy or pricing update? Did someone adjust a cloud configuration that led to this anomaly?
With this feature, Cloudability will automatically pull data about system changes and highlight them in the anomaly report, so teams can quickly identify the cause of the issue without guessing.
Example:
A system admin updates a cloud billing setting on Jan 29 to switch from on-demand to reserved instances.
Cloudability detects a cost spike on Jan 31 in a specific service.
The anomaly report now includes a marker showing: