Spend and periods¶
Almost every Costs page uses the date range in the top bar. Change it, and Overview, Spend Analytics, Anomalies, Inventory utilization, and related charts follow.
Period presets¶
Pick 7D, 30D, 3M, 6M, or 12M. On Spend Analytics you can also drag the spend trend to a custom range. Presets in the top bar restore a standard window.
When the selected range is three days or less, Overview and Spend Analytics zoom the trend to hours (UTC). Use Day / Hour on the chart header to switch. Wider ranges stay daily.
Budgets are different: the Budgets table is tied to a calendar month, not the 7D/30D bar. Use the month control on that page.
Spend¶
Spend is what Koltto stored from your cloud’s billing files (the Cost and Usage Report in S3 on AWS, cost reports on OCI), rolled up by day — and by hour when the chart is on Hour.
- Filter by provider (AWS vs Oracle Cloud), service, region, or scope.
- AWS credits: Spend Analytics can show totals as billed, or apply credits to regions as an estimate. That split is not the invoice line.
If the portal total and the bill disagree, check the same dates, the same accounts, and whether credits are included. Then run Refresh data → Cost. New billing files can lag up to 24 hours.
Scope¶
Scope is the cloud’s grouping for an account:
- Oracle Cloud: a compartment (and the tenancy as the root).
- AWS: the account (for now).
Spend Analytics and Inventory let you open a place, then the scopes under it that have data. It is not a Koltto team or tag — those belong to Allocations later.
Provider vs service¶
- Provider (or cloud) is AWS or OCI.
- Service is the product line on the bill (compute, object storage, database, …).
- Provider service on Overview is the vendor’s own name on the invoice line (for example an AWS service string).