Ability to assign and track investigation status of Cloudability cost anomalies in Cloudability UI

Problem:
Right now in the Cloudability Cost Anomly you get a list of alerts for unusual/unexpected cost increases. The content of the alerts themselves is useful and provides the information needed to dig deeper. The challenge comes when trying to take action on the alerts. There is no way to indicate who is responsible for investigating an alert further. There is also no way to indicate when an alert is brand new or has already been looked at. The result is that when you have more than one person who is responsible to overseeing these cost anomaly alerts, they often end up duplicating effort and wasting time investigating alerts that have already been looked at by other teammates because there is no way in Cloudability today to tell if a cost anomaly alert is brand new or has already been investigated.

Request:

Add mechanism in Cloudability Cost Anomaly UI to do the following for each alert:

Assign cost anomaly alert to another cldy user or your own user for ownership of the investigation
Have an alert status that can be set, to indicate the state of the investigation. E.g. (New, Under Investigation, Root Cause Identified, Resolved, False Positive)
Add free-form notes to track what is discovered while investigating an alert

Idea priority

High

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Ability to assign and track investigation status of Cloudability cost anomalies in Cloudability UI

Please enter your email address

RELATED IDEAS

Ability to assign and track investigation status of Cloudability cost anomalies in Cloudability UI