Google Cloud customer wakes up to $18,000 bill despite $7 budget
tomshardware.com
Google Cloud customer wakes up to $18,000 bill despite $7 budget
1–10 of 69 posts
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#2That is quite hostile to their consumers, no matter how they spin it. If you put a budget on something it should be capped.
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#3That is quite hostile to their consumers, no matter how they spin it. If you put a budget on something it should be capped.
I am the last person to defend Google Cloud and it's awful UX.
With that said, when you go to set a budget it warns you "Setting a budget does not cap resource or API consumption. Learn more." with a hyperlink to https://docs.cloud.google.com/billing/docs/how-to/budgets?_g...
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#4That is quite hostile to their consumers, no matter how they spin it. If you put a budget on something it should be capped.
I am the last person to defend Google Cloud and it's awful UX. With that said, when you go to set a budget it warns you "Setting a budget does not cap resource or API consumption. Learn more." with a hyperlink to https://docs.cloud.google.com/billing/docs/how-to/budgets?_g...
The only way I can read that is 'setting a cap does nothing' but reading that tells me that it only turns on email notifications. Not any better really. It's simply not a cap. It's an alarm.
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#5I think I read somewhere that calculating and limiting cloud usage costs is a really hard problem. But I feel that if Google were motivated to do it, they can do it. It's hard, not impossible. They just don't care to solve this particular problem.
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#6Earlier quoted context omitted.
I am the last person to defend Google Cloud and it's awful UX. With that said, when you go to set a budget it warns you "Setting a budget does not cap resource or API consumption. Learn more." with a hyperlink to https://docs.cloud.google.com/billing/docs/how-to/budgets?_g...
The only way I can read that is 'setting a cap does nothing' but reading that tells me that it only turns on email notifications. Not any better really. It's simply not a cap. It's an alarm.
Yes, there is no way to set a budget for Google Cloud. And alarms are delayed up to two hours (!)
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#7That is quite hostile to their consumers, no matter how they spin it. If you put a budget on something it should be capped.
I am the last person to defend Google Cloud and it's awful UX. With that said, when you go to set a budget it warns you "Setting a budget does not cap resource or API consumption. Learn more." with a hyperlink to https://docs.cloud.google.com/billing/docs/how-to/budgets?_g...
Click here to let the puppy life*
* By clicking here you agree to kill it
And you're defending that?
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#8I think I read somewhere that calculating and limiting cloud usage costs is a really hard problem. But I feel that if Google were motivated to do it, they can do it. It's hard, not impossible. They just don't care to solve this particular problem.
It's the same fundamental problem as view counters, something Google is famously good at solving. Eventually consistent solutions are well-understood, and wouldn't have these kinds of massive cost-overruns.
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#9I think I read somewhere that calculating and limiting cloud usage costs is a really hard problem. But I feel that if Google were motivated to do it, they can do it. It's hard, not impossible. They just don't care to solve this particular problem.
[deleted]
Re: Google Cloud customer wakes up to $18,000 bill despite $7 budget
#10I think I read somewhere that calculating and limiting cloud usage costs is a really hard problem. But I feel that if Google were motivated to do it, they can do it. It's hard, not impossible. They just don't care to solve this particular problem.
It's the same fundamental problem as view counters, something Google is famously good at solving. Eventually consistent solutions are well-understood, and wouldn't have these kinds of massive cost-overruns.
Depends on latency. 24 hour delays on an eventually consistent counter used for billing absolutely would cause this problem.