You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As cost estimation is based upon active resource on cloud account, it would be great if the tool can also retrieve the name of resources (it can be a bit frustrating to go back and forth from another tool to identify that this particular id means a particular known resource).
As such, it would be great to add another output field such as resource_name with the tag with key "Name" (if the customer has named the resource of course).
Besides it would be also great to let customer choose from which key retrieve a tag value (not only "Name" but any key that the user can specify, having "Name" as default key).
Thanks for considering my enhancement proposal.
Clément
The text was updated successfully, but these errors were encountered:
Hello,
Do you have any update on that feature ?
We are using the helm deployment with a prometheus -> thanos -> grafana structure.
We need a way to link cost metrics from osc-cost to labels / additional resources that we can find on the cockpit.
Uses cases could be :
dashboard view by environment label
total VM cost (VM + public IP + volumes attached + snapshots)
...
For the filtering by environment I could deploy osc-cost on each environment with filter-key-value and tell prometheus to add those labels to the metrics.
Hello,
As cost estimation is based upon active resource on cloud account, it would be great if the tool can also retrieve the name of resources (it can be a bit frustrating to go back and forth from another tool to identify that this particular id means a particular known resource).
As such, it would be great to add another output field such as resource_name with the tag with key "Name" (if the customer has named the resource of course).
Besides it would be also great to let customer choose from which key retrieve a tag value (not only "Name" but any key that the user can specify, having "Name" as default key).
Thanks for considering my enhancement proposal.
Clément
The text was updated successfully, but these errors were encountered: