Forget the "set and forget" alert setup GCP suggests. Their default thresholds are useless and engineers will just mute the noise. Here's what actually works, based on what they'll actually look at.
First, skip the Console UI for anything serious. Use the Budget API with a proper notification channel config. Key points:
* **Alert on burn rate, not just total.** A 90% monthly spend alert fires way too late. Set a second alert for >50% spend in the first 10 days of the month.
* **Target Slack/Teams, not email.** Pipe it to a dedicated #cloud-cost-alerts channel, not individual inboxes. Include the project ID and a direct link to the Budget Report.
* **Filter by service.** If your BigQuery costs spike, an alert on total spend is meaningless. Create separate budgets for Compute, BigQuery, and Network Egress.
* **The hidden cost:** commitment discounts. Your alert threshold must be *under* your committed use amount, or you get no warning before hitting the non-discounted rate.
Without these, your "alerts" are just a historical report you get to read after the invoice arrives.
Read the contract