Inventory Changes

Inventory Changes are resource diffs after your baseline scan — resources that appeared, and attribute, tag, or state diffs on ones that already existed.

Spend spikes live on Anomalies. The catalog of what is running is Inventory.

The first successful inventory is the baseline, not a list of changes. Rows show up after later inventory refreshes find something new or different.

How to use it

1. Click a service, status, or kind cell in the By service type matrix to filter. Click a cloud or account in the tree. Click the same cell again to clear.
2. Search by resource name. Open a row for the field-level diff.
3. Set status from the table: Open, Resolved, Silenced (30 days), or Dismissed. Resolved, silenced, and dismissed need a comment. Select rows to change status in bulk.

Kind chips:

• New (appeared) — the resource was not in the baseline.
• Changed — attributes, tags, or state moved.

Byte-sized diffs show a real delta when rounding would hide it.

Status

Status	Meaning
Open	Still in the queue.
Resolved	Expected or already handled (comment required).
Silenced	Hidden for 30 days, then it can reopen (comment required).
Dismissed	You will not pursue it (comment required).

When it stays empty

• No successful inventory yet — connect a cloud and wait for the first refresh (for Oracle Cloud, after you confirm the public key).
• Nothing has appeared or changed since the baseline.
• Filters hide the rows — clear search, status, kind, and the tree.