Act on spend
Allocation rules
Rules that name the owner of spend tags say nothing about, and share costs that belong to many owners.
Tags and named owners explain what they can. Allocation rules explain the rest, each written as a sentence anyone reading the figures can check. Find them under Allocation rules in the sidebar.
Two kinds of rule
- A rule that names an owner: lines that match its conditions belong to a team, feature, customer or user. What it explains is shown as inferred, as a tag's is.
- A rule that shares a cost: what is still unknown on a dimension for the lines it matches is shared among owners, shown as allocated:
- at fixed percentages, which must add up to exactly 100;
- evenly among the owners it names;
- by explained spend: in proportion to what tags, named owners and rules explain for each owner in the same month and currency, among the owners it names, or every owner if it names none.
Conditions
A condition compares one part of a billing line with one or more values: the provider, account, service, region, usage type, model, resource, or a tag by its key. It can ask whether the value is, is not, starts with or contains what you enter, or whether it is set at all. Values are compared exactly as the bill states them; tag keys match ignoring case and punctuation, as they do everywhere else. Every condition of a rule must hold.
Which rule applies
- What the bill and tags say always comes first: an owner named for a workspace, then the resource's tags, then the caller's tags. A rule never overrides them.
- Then rules that name an owner, in the order shown: the first that matches applies.
- Then a Kubernetes cluster divides what its nodes billed by what its workloads took, and a cloud's Databricks charges are divided by their usage: measured usage comes before a rule's assumption.
- Then rules that share a cost, in the same order.
- Then usage data divides what is still unknown and nothing else claims.
Use Move up and Move down to change the order.
Changes apply to every month
Every change to a rule, including turning it off or moving it, makes a new version, recorded with who made it, and every month is explained again with the rules as they now are. No figure, this month or any before it, rests on a rule that no longer applies. Versions shows each version as it was saved, and each rule shows what it explains in the latest month.
How sharing is calculated
A cost is shared once its month is explained, and each owner's part is rounded down to the tenth decimal place, so the parts never add up to more than the cost. What rounding leaves stays unknown. A cost with no one to share among, such as a split by explained spend among owners with none, stays unknown too. A split by explained spend is weighed by what tags, named owners and rules explain, never by other splits or usage data.
Who can change rules
Everyone who can see a project's costs can see its rules. Owners and admins create, change, reorder and delete them. Every change is recorded in Audit logs.