Managed Prometheus Workspaces Cost allocation based on metric labels

[rsheldon-ansira]

I would like to see provision made for working out the cost of metrics given one or more labels on metrics, much like you would do using Tags on EC2 resources. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html

The only advice that I got from AWS Support was to create separate workspaces and so track costs at that level, but I think this is counter-intuitive. We WANT to have a single workspace so it's simple for our users to create queries across accounts, environments, applications etc without having to worry about which workspace the data was ingested into. Given that AMP now supports 500m metrics in a single workspace, I would assume that allocating costs to different departments, teams etc in a company would be a common use-case, as different depts often have their own budgets, while tooks like prometheus are a shared resource that are centrally managed.

I would like to be able to define a set of "cost-allocation labels" and then be able to report on costs associated with these labels. This cost data would ideally be added as new metrics in prometheus so we can visualize them easily.

This cost would ideally include (and perhaps be split by) ingestion, strorage and anything else that is charged. If that's too hard just combining these in a single cost based on cost-allocation tags is fine with me.