Re:It's tough being an Azure fan
by bluediscussy22 on Friday September 24, 2021 @12:39AM
(#28638690)
It's funny this is coming up now. Just yesterday in GCP I was trying to figure out our billing and looking at what was costing such a huge amount. I couldn't figure out any way to map the actual service being used to the price on the normal reporting or even on the billing cost table export. The only way I could figure out how to do it was to enable log export. They used to have an option to download that as a file. They disabled that a while ago and now it's only available as a bigquery export. Which is exported every day. I was like "Why would that they do that ?" Oh cause now I have to set up big query and pay for all that. So I have to pay extra JUST TO SEE my detailed billing information. Pretty ridiculous.
[ Parent
| on HN ]
Re:It's tough being an Azure fan
by bluediscussy22 on Friday September 24, 2021 @01:01AM
(#28638791)
Here's the link to the actual cost for viewing my billing data.
https://cloud.google.com/billing/docs/how-to/export-data-big...
We really should revolt against this. I should be able to have a view of all of my billing without having to pay extra. It also shouldn't be hidden behind a bigquery export, it should be easy view what is being spent and what is causing it.
I used to work in GCP. The billing report UI in the billing account section shows per SKU usage. While detailed breakdown can be a nontrivial monster. Some customer may just launch thousands of VMs or data processing jobs per day.
Re:It's tough being an Azure fan
by bluediscussy22 on Friday September 24, 2021 @04:01AM
(#28639740)
Right that's correct. It shows SKU usage but not mapped to actual instance id. And we have the scenario you are talking about - lots of same sku with variable cost and no way to correlate it without using bigquery it seems
Re:It's tough being an Azure fan
by jiggawatts on Friday September 24, 2021 @03:57AM
(#28639716)
For all of the faults of Azure, they let you do this reporting directly in the Portal. You can slice and dice the data without having to spin up infrastructure.