Overview
The Cost page provides a historical view of infrastructure spend across your IT environment. It aggregates billing data from connected cloud platforms—Microsoft Azure and Amazon Web Services—alongside estimated costs for VMware, Microsoft Hyper-V and Kubernetes workloads, giving you a single place to understand where money is going and spot trends over time.
What's on the page
Summary metrics — Two headline figures appear at the top of the page: total cost and average daily cost for the selected time window.
Cost trend chart — A bar chart plots average daily cost over time. Use the Group by control to break the chart out by entity type or platform.
Entity cost table — Lists every entity contributing to cost, with the following columns:
• Name — the entity identifier in OneIQ.
• Type — the resource type, such as Azure Managed Cluster, VMware Host, Kubernetes Cluster, or Azure VM Scale Set.
• Platform — the underlying platform: Microsoft Azure, VMware, Microsoft Hyper-V, Kubernetes, or Applications.
• Average daily cost — average spend per day within the selected time window.
• Last month — total spend in the prior calendar month.
Controls
Time range — With costs, the selected time range does not restrict the data shown — you will always see the full extent of cost data available for your account. Users on a free license see up to 7 days of cost history, while users with an elevated (e.g. sponsored or premium) license see their full cost history.
Users with an elevated license may also move the origin date by clicking on the Live mode drop-down menu.
Group by — Controls how costs are aggregated in the chart and table:
• None (Aggregated) — all entities combined into a single total.
• Entity type — breaks costs out by resource type.
• Platform — groups costs by cloud or hypervisor platform.
How cost data flows into OneIQ
Microsoft Azure — Once your Azure environment is connected to OneIQ, cost and usage data is pulled in automatically. While no additional setup is needed, to include reservation cost data, assign the optional Reservations Reader role to the Pulse Service Principal as described in point #6 of Connecting to Microsoft Azure.
Amazon Web Services — For AWS environments, cost data appears on the Cost page automatically after ~48 hours once the AWS Cost and Usage Report has been enabled as outlined in Collecting Billing Data from Amazon Web Services.
VMware and on-premises — Cost estimates for VMware and on-premises workloads require that a cost profile be set up in your IT environment by the ITE owner. Suggested defaults are available, but if no cost profile is configured, costs for VMware and on-premises entities will not appear on the Cost page.
Notes
Cost history is only available from the date your Pulse connector was first connected and billing data collection was enabled. There is no retroactive backfill of historical cloud billing data. For VMware and other supported on-premises platforms, cost history begins from the date a cost profile was first applied.
The Cost page displays live data and requires an active Pulse connection. Cost data will not be available in frozen workspaces.