FinOps
11 rulesFinOps artifacts — cost, usage, and billing governance.
Cost FinOps Monthly Non Negative
info
experience: data-modeling
spec: costs
A cost monthly amount should be a non-negative number.
Cost FinOps Require Monthly
info
experience: governanceexperience: data-modeling
spec: costs
The `monthly` property of each cost should be present.
Cost FinOps Require Service
info
experience: governanceexperience: data-modeling
spec: costs
The `service` property of each cost should be present.
Document FinOps Budget Non Negative
info
experience: data-modeling
spec: document
budget should be a non-negative number.
Document FinOps Currency Iso4217
info
experience: consistencyexperience: data-modeling
spec: document
currency should be a 3-letter ISO 4217 code (e.g. USD).
Document FinOps Require Budget
info
experience: governanceexperience: data-modeling
spec: document
The `budget` property should be present.
Document FinOps Require Cost
info
experience: governanceexperience: data-modeling
spec: document
The `costs` property should be present.
Document FinOps Require Currency
info
experience: governanceexperience: data-modeling
spec: document
The `currency` property should be present.
Document FinOps Require Description
info
experience: documentationexperience: governance
spec: document
The `description` property should be present.
Document FinOps Require Name
info
experience: data-modelingexperience: governance
spec: document
The `name` property should be present.
Document FinOps Require Period
info
experience: consistencyexperience: governance
spec: document
A FinOps artifact should declare a period (e.g. monthly, annual) for the budget and costs.
11 of 11 rules shown · ← all artifacts