olOpsLyft Docs

Set budgets per team

Create budgets that alert the team that can act, not just the FinOps inbox.

Get allocation in place

Budgets per team need spend that's attributable to teams. See Allocate cost to teams.

Pick the scope

For each team, pick the accounts or services it owns. Enter them in the budget's filters, separated by commas.

Pick the period

Use Monthly for most teams. Use Daily for fast-moving costs such as data transfer or AI tokens, where a month is too long to wait.

Set the amount from history

Ask Iris What did [team] spend per month over the last 6 months? and set the budget a little above the recent average, or at the planned amount.

Add thresholds

Keep 80% and 100%. Add 50% for daily budgets if you want an early warning.

Notify the team

Add the team's Slack channel and its lead's email.

Turn on the ticket rule

Keep Budget exceeded 100% → ticket on so every breach has an owner and an SLA.

Clean up

Every month, open the Looks like tests group and delete budgets that are 5× or more below spend.

On this page