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.

Example: say a team sets a $5,000 monthly budget for its AWS production account. On day 18 it gets an 80% alert at $4,000, looks at the top services, and finds a forgotten EMR cluster costing $120 a day. Shutting it down that day keeps the month under budget.

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:
- Nothing selected: total spend across every cloud account in your org
- Accounts, providers, services and regions: pick one or more of each (for example the “AWS Production” account and Amazon EC2)
- Tags: match tag keys and values (for example team:platform)
- Virtual tag: one virtual tag from a cost category, with the values to count. Empty values count every value except Unallocated.
Filters combine, so a budget can cover one service in one account.

Start with account-level budgets, then add service-level budgets for your top 2-3 spenders.
Set the amount and thresholds
- Amount and period: the maximum you want to spend per month, quarter or year. For example, 5000 for $5,000/month.
- Alert thresholds: when to get notified, as percentages of the amount:
  - 80% and 100% are the defaults.
  - Add or remove any percentage up to 1000%, up to 10 thresholds per budget. Common choices: 50% (halfway check), 90% (last chance), 120% (overrun).
- Forecast alert: on by default. Alerts when spend is projected to exceed the budget by the end of the period.
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.
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.

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 are checked once a day at 11:00 UTC. They compare the spend projected for the end of the budget period with the budget amount, and fire once per period when the projection goes over.

They are controlled by the Forecast alert switch on each budget, which is on by default.

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 (08:00 UTC)	Evaluated 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 go to:

Email: every active admin of your organization, except anyone who turned off budget alerts on their Profile page. There is no per budget recipient list. The email includes the budget name, current spend, threshold hit, and a link to the console.
Slack: your Slack workspace’s default channel through the Xplorr Slack app, or the organization’s Slack webhook when the app is not connected. There is no per budget channel picker.

Outbound webhooks do not carry budget events today.

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.
Not connecting Slack. If your team lives in Slack, email-only alerts get ignored. Connect the Slack app or set an organization Slack webhook.
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)
The people who should get budget emails are admins, with budget alerts on in their profile
Slack connected (if your team uses Slack)
Forecast alert left on for production budgets
Budget amounts reviewed and adjusted monthly

FAQ

When do budget alerts reset? At the start of each budget period: the 1st of the month, of the quarter (January, April, July, October) or of the year. Spend tracking resets to $0 then.

Can I set quarterly or yearly budgets? Yes. A budget’s period is monthly, quarterly or yearly. Weekly budgets are not supported.

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. Add tag keys and values to the budget’s scope (e.g., team:platform or environment:production), or one virtual tag.

How is a budget scoped to a virtual tag counted? The virtual tag’s rules are applied to the budget period’s cost, and only the cost they assign to the chosen values counts. With no values chosen, every value except Unallocated counts. One virtual tag per budget. If the virtual tag is deleted, or a chosen value no longer exists, the budget shows a warning and that part of the scope matches no spend rather than all spend. See Cost Allocation.

How quickly do alerts fire after crossing a threshold? Thresholds are checked once a day at 08:00 UTC, with a second pass at 09:00 UTC, after the daily 02:00 UTC sync. Each threshold alerts once per period. Provider billing data also lags by up to a day or more.

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
Connect Slack so alerts reach the team, not just admins’ inboxes

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