Hello Noah,
Even though we do not see a use case for the feature you described, you seem to have a solid use case. Other approaches could have been used to "rename"/"map" tenant_id to project_id, such as with Dynamic pollsters in Ceilometer. However, the argument you present seems solid to me.
I would say that if you open a patch, we would happily review it :). AS long as things are backwards compatible, tested, and well documented, we would for sure merge it.
Hello! I am currently trying to get CloudKitty to work with the Prometheus Collector and PyScripts. I noticed that the scope_key for Prometheus can only be changed once in the global configuration file. This was a problem for me because we need different scope_keys for different metrics. Many of the metrics still need the scope key "tenant_id" and some others "project_id". I have found in the documentation of CloudKitty no way to change this for each metric, so I have internally changed something in the source code and added the function to set the scope_key for each metric individually. I just wanted to ask if you would be interested if I submit the small change upstream?
Thank you. Regards
Noah Feldt
--