FinOps KPIs
Key Performance Indicators (KPIs) provide critical insights that enable you to actively manage, optimize, and forecast cloud spend. The FinOps KPIs page offers enhanced visibility into cloud spend, usage, and optimization trends, supporting proactive cost management, waste reduction, and data-driven budgeting and financial planning.
On the FinOps KPIs page (Cloud > Cost Optimization > FinOps KPIs), you can access vendor-specific KPIs with visualizations for current and historical (up to 12 months) cloud spend, usage, and optimization.
The following cost KPIs are available to track key metrics:
| • | Commitment Coverage History—This KPI measures how effectively long-term commitments (such as Reserved Instances or Savings Plans) are leveraged to reduce the overall cloud spend. The KPI displays the percentage of eligible compute usage covered by commitments over time (up to 12 months), with a breakdown by purchase option. Higher coverage indicates greater savings. By tracking this KPI, you can: |
| • | Understand how much of your ‘reservable’ cloud spend is running in the most cost-efficient way. |
| • | View how much of your usage is covered by commitments. |
| • | Inform future commitment purchasing strategies. |
| • | Savings Realized—This KPI measures the actual cost savings on your cloud bill by using commitment-based discounts (such as Reserved Instances or Savings Plans), compared to what you would have paid at standard on-demand rates. The KPI displays realized savings for the current month and the previous 12 months, tailored for each cloud vendor and commitment type. By tracking this KPI, you can: |
| • | Compare savings across cloud vendors to identify where your organization achieves the greatest value. |
| • | Guide future purchasing and optimization decisions by reviewing trends in realized savings and discount rates. |
| • | Compute Cost Per Hour Per Month—This KPI measures the average cost incurred for compute resources (such as virtual machines or instances) per usage hour, calculated each month. The KPI displays the amortized compute spend divided by the total number of compute hours consumed in that month, providing a normalized view of compute efficiency over time. You can analyze this KPI by date and by purchase option (such as On-Demand, Reserved Instances, Savings Plans) to gain deeper insights. A lower cost per usage hour indicates better optimization and less waste. By tracking this KPI, you can: |
| • | Identify trends in compute costs over time to spot changes in efficiency. |
| • | Compare compute costs between different cloud vendors and purchase options to evaluate cost efficiency. |
| • | Identify higher-than-usual compute costs and take quick action to optimize spending. |
| • | Promote increased use of Spot instances and improve coverage of commitment discounts to optimize costs. |
| • | Storage Cost Per Hour Per Month—This KPI measures the average amount you spend on storage resources (such as block, object, or file storage) for each gigabyte (GB) used per month. The KPI displays the total monthly storage cost for each storage category divided by the total GBs used in that category, providing a normalized view of storage cost efficiency over time. By tracking this KPI, you can: |
| • | Identify trends in storage costs per GB to spot changes in efficiency. |
| • | Detect higher-than-usual storage costs per GB so you can take action to optimize spending. |
| • | Database Cost Per Hour Per Month—This KPI measures the average amount you spend on database resources (such as managed database services or database instances) for each hour of usage, calculated monthly. The KPI is calculated by dividing the total monthly database cost for each database category by the total number of database usage hours in that month. By tracking this KPI, you can identify trends in database costs per hour to spot changes in efficiency. |