Track resources via current tags
It would be nice to be able to query the Consumption API against the tags currently applied to resources and have the option to identify past usage before those tags were applied.
This should only be an option - there are certainly cases where you might prefer to have the tags as of the date of usage.
Dillon Brown
shared this idea
This is definitely needed!
Let us know if there are specific cases where you’d like to be able to look at costs by the tags when they were applied vs. the current state of tags viewed retroactively. Understanding your needs will help ensure we cover the specifics for you.
3 comments
-
Michael Waddell
commented
In order to match up resource costs against our internal project-based budgeting, we need a way to associate resources flexibly and in a way that can be changed retrospectively as needed. So far, tags is the best approach we've found, but it's not quite what we need.
Our ideal solution would be something like the following. Every resource gets a "billing project" tag. This tag could default to blank when a new resource is created, or it could be initialized to match the "resource group name". When this tag is changed, you are asked to specify if the change applies only to the current billing cycle (the default) or if it applies retroactively (and if so, how many months backwards from the current billing cycle it applies to). These changes should immediately be visible in the Cost Management graph/export UI.
-
Lipsky, Eugene
commented
Looking for retroactive tagging.
Use case is inconsistent tagging on resources making it difficult to generate accurate cost reports. We can add a new consistent tag to all Cosmos DBs today and start seeing their cost/projected cost going forward, but would like to easily be able to generate a report breaking down cost per DB over the last year.
-
Richard Hooper
commented
I agree. It would be good to maybe look at adding this feature. I can see many times, specially when people are just starting with tagging resources, they would like to see how much that tag cost them previously.