Feature Requests

Currently, when a user creates a custom perspective and doesn’t complete the setup, the perspective still gets saved in the list. These incomplete perspectives appear with an orange box and an exclamation mark, which leads to unnecessary bloat and confusion for users trying to identify valid perspectives. Ask: Don’t allow unfinished or incomplete perspectives to be saved. Only save a perspective once the setup is successfully completed.

Reporting and monitoring of User engagement is an essential part of culture change in an organisation. The Audit trail is the only record we have of end users logging in and creating or editing Perspectives and Dashboards. Please enhance the trail by: Allowing "exclude" in filters Enable Column sorting Provide export to CSV capability Recognising automation activity as a User type Allowing Scheduled reports Allow more than 1 record type in a filter, eg perspectives and Dashboards Allow the choice to report distinct Users as opposed to distinct transactions OR Bring the data into the BI Dashboards as a tile type

Allow for drill down filtering in the line graph view when clicking the data point, similar to behavior when clicking the top of the bar graph view. This would make the behavior consistent, and allow for usage of that fast filtering feature without toggling back to the bar view.

As of now if we have cost preferences have setup we cannot see anomalies in perspectives. The request is to ensure that the cost preferences set for an account are taken into account during the anomaly detection process, providing more accurate and aligned results with user-defined settings.

Allow a recommendation to remain as listed once it has been put into a new "In Progress Status". This gives the engineer a chance to return to the tool to register the action taken and provide a fair estimation of the actual savings gained. Sometimes it takes a few weeks before the savings can be seen in enough data to prove the value of the actioned recommendation. A5t the moment the Engineer only has until the next update, when the recommendation may just disappear! Mad!

We need some sort of alerting outside of Harness when an autostopping rule fails to restart an instance as scheduled. Harness shows logs when an instance fails to restart, but we need an alert to bring attention to it

Currently, the scheduled report email displays the total cost and the cost for the previous month. However, the report can be confusing due to a lack of clarity around the time ranges. To improve this, we suggest explicitly labeling the figures with their respective time ranges: The left-hand figure should be labeled “The last [duration]” The right-hand figure should be labeled “Previous [duration]” This will help users better understand the context of the reported costs.

Hi Team, Currently while creating perspective, labels and tags are shown for all the sources in drop down causing confusion if the tags named same for K8s and cloud resources. Cloud resource tags are normalised and K8s tags are not which again cause confusion as the user is not able to determine the source of the tag. Request you to please add some source indicator in the tags that can make it clear from where this label is getting populated.

We expect tag based instance selection feature for auto stopping rules . Right now the selection of instances are static in nature in which we have to select instance ids one bye one to create rule . Our expectation is that rule will select all the instances that are tagged with a specific key and value pair(Similar way how AWS instance scheduler works) . Our aim is to create the rules via terraform but with current limitation of passing instance ids manually one by one is a tedious task . We expect it for both RDS and EC2 .

Add the possibility to show average cost within Perspectives, e.g. when inspecting Cost for the last month, showing additionally average cost per day. On top: The possibility to show average cost on a weekday and/or weekend day.