Feature Requests

Please add a link, via button or menu select from a Perspective to Recommendations based on the filtered selection in the Perspective. For this use case, user_applicationci is desired.

Right now, recommendations in CCM are nearly useless for United, as there is no way to easily sort through the 5000+ recommendations by Cost Bucket or Label.

When calling CCM recommendation details API with different times the recommendations for Percentile and guarenteed do not change As per the current API support, we generate Percentile based recommendations based on last 8 days of data only. There is no support of recalculating this recommendation based on passed time range in API. Histogram value changes with the given time range in the API and UI uses the same histogram to show recommendations. We need this functionality with api

For traffic based autostopping at scale, we need all VM's to power onprior to their patch window and then shut down after patch window is complete. Currently, the only way to do this is to bulk disable the rules which is a cumbersome effort. This should be done in the rule itself so that the patching can occur.

Could you guys add the ability to create a autostopping rule in Terraform that starts out in a dry run or disabled state? I think we have a need for that and while we can create a rule and then change it in the UI, I'd like the ability to create one from Terraform. Thanks!

Add support for NG API key while creating a Kubernetes connector with auto stopping. As of now it redirects to harness First gen.

As of now When we apply the NOT_IN filter on any field, we only consider the non-null values which makes the perspective drop the costs under No product. The ER is to consider null values when using NOT_IN filter

For the 'Forecast Cost' value inside of a Perspective is meaningless. It currently always shows the next 30 days, which is useless when trying to forecast costs for a Single month or For a quarter. What should happen is the Forecast value should respect the Data Range and the Period filters. If you are selecting "This month" and "Daily" it should forecast to the end of "this month". Details: * when Selecting show "this month" the 'forecast cost' value should forecast to the end of "this month". * when selecting show "this year" it should show the forecasted value for the remainder of "this year"

Currently we use https://aws.amazon.com/solutions/implementations/instance-scheduler-on-aws/ and for nonprod RDS/EC2 type resources we do not allow creation with a "Schedule" Key and appropriate value. This means any nonprod resources created will be stopped based on the Schedule tag value supplied. Is there any way we can use Harness AutoStopping or features to do something similar to enforce autostopping on nonprod resources?

anomalies do not decrease when marked as a false positive, only a message appears but leaves the anomaly in the same list