Budgets, anomalies and savings
How budgets are forecast, how anomalies are detected, and when a saving counts as verified.
On this page
Budgets and forecasts
- A budget's scope can be any slice of spend: a business unit, team, provider, service category or the whole bill.
- The forecast adds the remaining days to month to date, each at the median of that weekday over the last four weeks.
- Each forecast is kept and scored against the closed month.
- Each threshold alerts once and resolves once.
Anomalies
- Each day's spend on each service in each account is compared with the median of its previous 28 days.
- A day is flagged when its robust score passes 3.5 and the extra spend passes your minimum. Both are organization settings.
- Series with fewer than 14 days of spend, such as monthly fees, are skipped.
- Each anomaly lists the resources that drove it.
Savings
| State | What it means |
|---|---|
| Open | A monthly estimate, with its evidence, method, confidence and risk |
| Implemented | Your team made the change and marked it done. Still an estimate |
| Verified | The resource's cost in the 14 days after the change, compared with the 14 days before |
UnitVane changes nothing
It reads billing data only. Your team makes each change in the cloud, or for Kubernetes through change proposals.
Need help with this guide?Contact support