Set Up Budgets and Alerts

01

Decide where budgets apply

Budgets can be set at organization, team, cloud account, cluster, namespace, or service level. Nested budgets roll up automatically, so a team budget aggregates the namespaces and services beneath it.

02

Create a budget

Set a monthly target and the thresholds you want to be warned at — typically 75%, 90%, and 100% — plus the recipients responsible for that scope.

03

Choose alert channels

Route alerts to where the team already works.

• Slack and Microsoft Teams
• Discord
• Email
• Jira (auto-create tickets)

04

Turn on anomaly detection

Enable anomaly detection so unusual spikes are caught within hours, each with a probable root cause — a deploy, scaling event, or config change — instead of a bare number.

05

Add guardrails

For non-production scopes, set spend guardrails that cap runaway costs from misconfigured autoscaling or forgotten resources before they compound.