topic Query Cost Allocation for Short-Lived Environments Using DQL in DQL

Query Cost Allocation for Short-Lived Environments Using DQL

ftmazzone — Wed, 17 Dec 2025 10:10:42 GMT

Hello,

For our short-lived environments and servers, we would like to use the cost allocation feature and provide to standard users an option to view the consumption per cost center. The cost center in our case is unique for each environment even if it short- lived.

Is there an option to allow using any `dt.cost.costcenter` value instead of using an allow list ?
Or is there an option to view all the `dt.cost.costcenter` values not present in the allow list ?

Re: Query Cost Allocation for Short-Lived Environments Using DQL

IzabelaRokita — Wed, 17 Dec 2025 10:10:56 GMT

Hey @ftmazzone ,
I just wanted to check in and see if you still need help with this. If so, I’d be happy to look into it for you! 😊
Please let me know what works best for you.

Re: Query Cost Allocation for Short-Lived Environments Using DQL

ftmazzone — Wed, 17 Dec 2025 10:18:57 GMT

Hello @IzabelaRokita ,

Thanks for your reply. Yes, this is definitely a topic that is still important for us. 🙂
Currently, we have an AWS lambda that queries the host group names and Kubernetes cluster names for each environment in order to add them in the allow list. As this process is daily, the test or performance Kubernetes clusters won't have a valid cost center value.