Cloud Budget Alerts: Set Up Spend Notifications in Xplorr

import { Steps } from ‘@astrojs/starlight/components’;

Cloud Budget Alerts

A budget alert tells you when your cloud spend crosses a threshold — before the bill arrives. Xplorr supports both fixed-threshold alerts (“you’ve hit $4,000 of your $5,000 budget”) and predictive alerts (“at current pace, you’ll exceed $5,000 by month end”).

Why Budgets Matter

Without budgets, cost surprises are the default. A developer spins up a p3.8xlarge for testing and forgets about it — $75/day turns into $2,250 by month end. A misconfigured auto-scaling group doubles your compute fleet overnight. Budgets catch these situations early enough to fix them.

Real example: A team set a $5,000 monthly budget for their AWS production account. On day 18, they got an 80% alert at $4,000. They investigated and found a forgotten EMR cluster burning $120/day. Shutting it down saved $1,400 for the rest of the month.

Creating a Budget from the Dashboard

Go to Budgets

In console.xplorr.io, click Budgets in the left sidebar and click New Budget.
Set the scope

Pick what the budget covers:
- All accounts — Total spend across all AWS + Azure + GCP accounts in your org
- Single account — One specific cloud account (e.g., “AWS Production”)
- Service — A specific cloud service (e.g., Amazon EC2, Azure Virtual Machines, BigQuery)
Start with account-level budgets, then add service-level budgets for your top 2-3 spenders.
Set the amount and thresholds
- Monthly budget amount — The maximum you want to spend. For example, 5000 for $5,000/month.
- Alert thresholds — When to get notified:
  - 80% (default) — Early warning. Enough time to investigate and act.
  - 100% (default) — You’ve hit the limit.
  - Custom — Add any percentage. Common choices: 50% (halfway check), 90% (last chance).
Tip: Set your budget at 90% of your actual limit. This gives you a buffer — your 100% alert fires when you’re really at 90% of what you can afford.
Choose notification channels
- Email — Your account email by default. Add more recipients (comma-separated).
- Slack — If you have the Slack integration configured, select a channel. Budget alerts post with the budget name, current spend, and percentage.
Click Create Budget

The budget starts tracking immediately against your current month’s spend.

Creating a Budget via Claude (MCP)

If you have the MCP server connected, create budgets through natural language:

“Create a $5,000 monthly budget for my AWS production account and alert me at 80% and 100%”

“Set a $500/month budget for our GCP dev environment”

“Show me all my current budgets”

“Update the production budget to $6,000”

“Delete the staging budget”

The MCP server has four budget tools: create_budget, list_budgets, update_budget, and delete_budget.

Creating a Budget via API

curl -X POST https://api.xplorr.io/api/v1/budgets \
  -H "Authorization: Bearer xplorr_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "AWS Production",
    "amount": 5000,
    "currency": "USD",
    "period": "monthly",
    "cloud_account_id": "acc_abc123",
    "alert_thresholds": [80, 100]
  }'

Response:

{
  "id": "bud_xyz789",
  "name": "AWS Production",
  "amount": 5000,
  "currency": "USD",
  "period": "monthly",
  "cloud_account_id": "acc_abc123",
  "alert_thresholds": [80, 100],
  "current_spend": 3200,
  "current_percentage": 64,
  "created_at": "2025-03-01T00:00:00Z"
}

Budget Templates

For common setups, use these as starting points:

Small team (1-2 cloud accounts, <$5K/month):

1 budget per account, $5,000 limit, alerts at 80% and 100%

Mid-size team (5-10 accounts, $10K-$50K/month):

1 org-wide budget for total spend
1 budget per production account
Service-level budgets for compute and storage

Enterprise (10+ accounts, $50K+/month):

Org-wide budget with alerts at 50%, 80%, 100%
Account-level budgets for each business unit
Service-level budgets for top 5 services
Tag-based budgets by team or project (if using allocation rules)

Predictive Budget Alerts

Standard alerts fire when you cross a threshold. Predictive alerts fire when your forecast shows you’ll cross the threshold by month end, even if you haven’t reached it yet.

Example: On day 12 of the month, you’ve spent $2,800 of a $5,000 budget (56%). A standard alert wouldn’t fire until you hit $4,000 (80%). But if your daily run rate is $250/day, Xplorr forecasts you’ll hit $7,500 by month end — a predictive alert fires immediately.

Predictive alerts use the same get_cost_forecast engine that powers the dashboard forecasting feature. They run daily and evaluate whether the projected end-of-month spend exceeds each budget threshold.

To enable predictive alerts, toggle Forecast-based alerts when creating or editing a budget.

Anomaly Alerts vs Budget Alerts

	Budget Alert	Anomaly Alert
Trigger	Spend crosses a fixed dollar threshold	Spend spikes vs 7-day rolling average
Good for	Monthly spend caps, cost governance	Unexpected surges (runaway instances, misconfigurations)
Setup	You define the amount and thresholds	Automatic — no configuration needed
Example	”You’ve spent $4,000 of your $5,000 budget"	"EC2 spend jumped 340% vs last week”
Timing	Evaluated daily	Evaluated every sync (every 6 hours)

Use both together. Budget alerts guard your spending limits. Anomaly alerts catch surprises even if you’re under budget.

Notification Channels

Budget alerts can go to:

Email — Sent to the addresses you specify when creating the budget. Includes budget name, current spend, threshold hit, and a link to the dashboard.
Slack — Posts to a channel you select. Requires the Slack integration (configured in Settings > Integrations). The message includes the same details plus a formatted breakdown.
Webhook — Coming soon. Will POST a JSON payload to a URL you specify.

Common Mistakes

Setting budgets too high. A $50,000 budget when you spend $10,000/month won’t catch problems. Set budgets 10-20% above your expected spend.
Only using 100% alerts. By the time you hit 100%, it’s too late to act. Always include 80% (or lower) as an early warning.
Forgetting to add Slack. If your team lives in Slack, email-only alerts get ignored. Add the Slack channel.
Not reviewing budgets monthly. Your spend changes. A budget that was right 3 months ago may be too low or too high now. Review and adjust monthly.

Setup Checklist

At least one budget created per cloud account
Alert thresholds set at 80% and 100% (minimum)
Email notifications configured with the right recipients
Slack channel configured (if using Slack integration)
Predictive alerts enabled for production accounts
Budget amounts reviewed and adjusted monthly

FAQ

When do budget alerts reset? At the start of each calendar month. Spend tracking resets to $0 on the 1st.

Can I set weekly or quarterly budgets? Currently only monthly budgets are supported. Weekly and quarterly options are on the roadmap.

What happens when I hit 100%? You get notified. Xplorr does not automatically stop or limit your cloud resources — it’s a monitoring tool, not an enforcement tool. You decide what action to take.

Can I budget by tags? Yes, if you have allocation rules configured. Create a budget scoped to a tag-based allocation group (e.g., team:platform or environment:production).

How quickly do alerts fire after crossing a threshold? Budget evaluation runs after each data sync (every 6 hours). In the worst case, there’s a 6-hour delay between crossing a threshold and receiving the alert.

Key Takeaways

Start with one budget per cloud account at 80% and 100% thresholds
Enable predictive alerts for production — they catch overruns days earlier
Use both budget alerts and anomaly detection for full coverage
Review and adjust budget amounts monthly as your spend changes
Add Slack notifications so alerts reach the team, not just one inbox

MCP Server — Create and manage budgets through Claude
Connect AWS — Get AWS cost data into Xplorr
Connect Azure — Get Azure cost data into Xplorr
Connect GCP — Get GCP cost data into Xplorr