A forecast from your real burn rate
Month-to-date spend is only half the picture. CloudMonitor projects the month end by taking what you have spent so far and adding the average daily spend of the last seven complete days for each day that remains. Seven days is long enough to smooth out a single odd day and short enough to react when your baseline really changes. The forecast sits next to last month’s total so the direction is obvious.
Budgets that alert once
Create a budget for all clouds, or for AWS or Azure on its own, with a monthly limit and an alert threshold anywhere between 1% and 100%. Budgets are evaluated hourly against month-to-date spend. When spend crosses your threshold the workspace owners and admins get one alert, and when it reaches 100% they get one more. Neither repeats within the same calendar month, so a budget never turns into noise.
Where budgets fit in your FinOps loop
Budgets tell you that the month is drifting; anomaly detection tells you which day it started, and the cost optimizer tells you what to do about it. The month-to-date figure, forecast, daily burn and budget status are also part of the scheduled report, so stakeholders see the same numbers without logging in. If you are just starting out, our plain-English guide to FinOps explains the loop.
Coverage
Spend comes from AWS Cost Explorer and Azure Cost Management. Google Cloud cost data requires a BigQuery billing export, which CloudMonitor doesn’t read yet, so Google Cloud budgets aren’t available today.