Skip to content
Browse documentation
OperateOperator1 min

Data sources and freshness

Check how provider billing, inventory, utilization, security, pricing, and recommendations are collected, dated, and marked missing or stale.

On this page

  1. Task and prerequisites
  2. Provider source split
  3. Freshness
  4. Missing metrics need a separate check

Task and prerequisites

Use this guide when costs, inventory or findings appear stale or incomplete. You need access to the affected connection and the selected period.

Provider setup changes need an authorized provider administrator. Keep the relevant provider guide available; Azure billing, AWS pilot collection and Google Cloud billing exports use different prerequisites.

Costframe collection remains read-only.

Provider source split

Costframe collects billing, resource inventory and utilization through different provider APIs. Native recommendations, security evidence and catalog prices also have their own availability.

A successful read from one source does not establish that every other source is current or accessible.

Freshness

Check the connection's validation time, the audit's observation window and the billing period separately. For example, a role may validate today while a finding still refers to last week's resource snapshot.

A resource absent from today's inventory can still have retained charges from an earlier period; that absence does not prove deletion or a saving.

Missing metrics need a separate check

If inventory is available but utilization is permission-limited or unavailable, you can review the resource configuration but cannot treat missing activity as zero activity. Check the capability's stated limitation and observation period before deciding whether to resize or remove the resource.

Find your next task

Browse setup, operation and recovery guides ↗Recover from a failed connection, audit or export ↗Ask a question with the safe support reference ↗

Related docs