Data refresh

Koltto does not call the cloud on every page load. Pages read data that was already pulled. Account → Refresh data is where you pull more.

What a refresh covers

Kind	What it updates
Inventory	The catalog of resources (what you have).
Cost	Daily spend from the bill (AWS: CUR files in your S3 bucket; OCI: cost reports in Oracle’s report bucket).
Metrics	Utilization (CPU, and similar) used by Inventory and Opportunities.

A manual Cost or Metrics refresh covers about the last 7 days. The overnight refresh covers about 2 days. Koltto also refreshes automatically overnight.

Need a longer cost history than that? Email support@koltto.com.

How to run one

1. Open Account → Refresh data.
2. Choose Inventory, Cost, and/or Metrics.
3. Select one or more clouds.
4. Start the refresh. Watch the run strip; cancel there if you need to.
5. Expand a row in Refresh history for per-service steps.

Only one company-wide refresh runs at a time. Manual runs have a short cooldown — wait if you see that message.

When it runs by itself

• Adding a cloud account starts a first inventory refresh. For Oracle Cloud, that happens after you add Koltto’s public key and confirm it in Koltto — see Oracle Cloud.
• You can refresh one resource from Inventory when you only need that row.
• Overnight jobs keep cost and inventory from going stale.

If Overview, Spend Analytics, or Anomalies looks empty after a new account, run Cost (and Metrics if you care about Opportunities). Inventory alone will not fill the spend charts. A brand-new AWS CUR or OCI cost report can take up to 24 hours before the first file is ready; Cost stays empty until then. Inventory Changes fill in after later inventory refreshes compare against the first successful scan.