Asset Inventory
The Inventory view lists every resource the discovery pipeline has found, across every connected account and region.
Columns
| Column | What it holds |
|---|---|
| Asset | The resource name, with its type |
| Provider | Which cloud it was discovered in |
| Region | The region it lives in |
| Account | The account or subscription that owns it |
| Monthly cost | What the resource costs per month |
| State | The resource's current lifecycle state |
| Last seen | How long ago discovery last confirmed it exists |
Why cost is on a security-adjacent inventory
Because the two questions are asked by the same person about the same resource, ten minutes apart. An inventory that cannot answer "what does this cost" sends its user to the billing console, where the resource is identified differently and connected to nothing. Estate stamps monthly cost onto the asset row so the estate is answerable to a finance question without leaving the page.
For the full cost picture — attribution, forecast, budgets, anomalies and savings — see Onam FinOps, which is a separate product.
Last seen, and why it matters
Every asset carries the time discovery last confirmed it. A resource that stops appearing does not silently vanish from the list; its last-seen time ages, which is how decommissioned-but-not-really infrastructure becomes visible.
If last-seen times across a whole account are ageing together, that is a pipeline problem rather than a decommissioning event. Check Pipeline before concluding anything about the account.
Pagination on large estates
Inventory listings are keyset-paginated. On estates past a few hundred thousand assets, offset pagination degrades badly enough to exceed the query timeout — keyset paging holds a constant cost per page regardless of how deep you are in the list.