22 lines
926 B
Markdown
22 lines
926 B
Markdown
|
# Monthly technical usage observations
|
||
|
|
|
||
|
|
After each provider billing period, add `YYYY-MM.json` conforming to
|
||
|
|
`schemas/monthly-resource-observation.schema.json` with
|
||
|
|
`record_type: usage_observation`. These records contain technical and labor
|
||
|
|
observations. Authoritative booked financial actuals come from fin-hub and are
|
||
|
|
referenced during reconciliation rather than copied into a second ledger.
|
||
|
|
Set `forecast_ref` to the forecast file used for the decision. Evidence should
|
||
|
|
identify, without secrets, the provider usage export/invoice, PostgreSQL/CNPG
|
||
|
|
measurement, restore drill, and internal time record.
|
||
|
|
|
||
|
|
Required proxies are database GB, provider stored GB, WAL GB, restore egress,
|
||
|
|
write/read requests, infrastructure invoice cost, internal labor hours/cost,
|
||
|
|
and total cost. Also capture backup success, maximum observed RPO, and restore
|
||
|
|
RTO when available.
|
||
|
|
|
||
|
|
Run:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
make variance ACTUAL=data/actuals/YYYY-MM.json
|
||
|
|
```
|