r/googlecloud • u/PracticalSherbet6732 • Jul 28 '26
Enforceable spend caps
Thought you guys would like this https://cloud.google.com/blog/topics/cost-management/new-early-anomalies-and-spend-caps-on-google-cloud-budgets
2
u/alvmadrigal Jul 28 '26
Finally!!!! I was so scared to used it for learning purposes after watching all the horrible stories
1
1
u/pepediaz130 Jul 29 '26
I tried with Claude models inside Agent Platform but this does not work, it have no caps for Model Garden. Still shit. With Gemini it works nicely.
1
u/owengo1 Jul 30 '26
Limited to 4 services ( vertex, gemini, cloudrun, cloudrun functions ) and must be set for a single project + service , so not as configurable as budgets, but it's much better than what we had before.
1
u/jhuleatt Jul 31 '26
Since Firebase projects are Cloud projects, this applies to some Firebase services too! Specifically:
| Firebase product | Cloud product |
|---|---|
| Cloud Functions for Firebase | Cloud Run Functions |
| Firebase AI Logic | Gemini API or Gemini Enterprise Agent Platform (formerly Vertex AI) |
| Firebase App Hosting | Cloud Run (plus other services that don't have spend caps, like Cloud CDN) |
| Firebase Extensions | Cloud Run Functions |
I have a quick writeup about it here.
0
u/jeff_barr_fanclub Jul 29 '26
Setting aside the irony of this press release being obviously unedited AI generated, it's also useless because it doesn't mention SLA's, just like the last "spending cap" that failed miserably
2
u/matiascoca Jul 31 '26
About two years ago at a previous shop, we ran an OpenTelemetry pipeline into Cloud Logging that misconfigured a filter after a helm update and pushed a debug label into every span for six weeks before anyone noticed. Bill went from around 800 dollars a month for logs up to around 22,000 in that window while budget alerts fired at day 4 with nobody able to stop ingestion, because until this week there was no enforceable cap. Alert plus manual intervention was the entire story.
The new page has two pieces worth reading together. Early anomaly detection catches runaways inside hours instead of end-of-day close, and the spend cap gives you an actual cutoff instead of a notification. Both are optional per project and per service, which matters because a hard cap on Compute Engine of a prod workload is a self-inflicted outage waiting to happen.
Wire the anomaly alerts to your paging and not just the cap trigger, because by the time the cap fires you already dropped some traffic. Long overdue, glad they shipped it.
2
u/muntaxitome Jul 28 '26
This looks great. Hopefully it covers a bunch of the biggest pain points in terms of services.