Feature Requests

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.

We have over 60 Kubernetes clusters that all have their own delegates, and some of those clusters are created/destroyed regularly. We strive to have cluster provisioning 100% automated, and It would be very helpful if CCM connectors could be automatically added when setting a value true in the helm values.yaml files for the delegates. We find that users forget to go into CCM and set up the connector to collect data because it's a manual step. We discover that someone forgot to do this work weeks/months later when we want to look for cost data, only to find it isn't there. (Side note: We would also like to avoid having to add additional automation that calls harness APIs after a cluster is built.)

We need support for awsbillingperiodstartdate and awsbillingperiodenddate in perspectives