maxb-hystax

Can you please provide details?

@gpuligundla sure, you are welcome!

Hi @kartraj, OptScale counts expenses for both accounts separately, meaning that root account expenses track only expenses for resources which belong to the root account itself. Could this be the...

Are you going to publish it in your fork? Maybe we'll be able to incorporate it into the code soon.

Hi! Azure EA subscriptions don't provide expenses data in usual way, so you need to connect such accounts with import_scheme: "raw_usage" parameter. You can refer to https://github.com/hystax/optscale/blob/be70d943019d88a5c4ae778765a74ef66e6dca7d/diworker/diworker/importers/azure.py#LL139C2-L139C2 for the details.

It should be set when calling cloud account creation or patch API. Further version which we plan to publish includes autodetection of necessary import scheme, but for now it is...

Hi @elikkatzgit Please check Herald service logs (container_name:*herald*)in Kibana (port 30081) - they should describe what's happening there.

Hi Thomas, As I think, such resources with monthly/annual pricing will still be charged more or less continuously, not once per month/year. How do you think?

Hi! Yes, we've started implementation and aim to deliver support AWS CUR 2.0 in April'24. You'll need to update connection settings, while we are going to maintain smooth transition for...

Closing - CUR 2.0 is support is delivered.