Which of the following is NOT a key metric to monitor in a FinOps approach? (Select One)

FinOps is a practice focused on bringing financial accountability to the variable spend model of the cloud. Its key metrics are centered on understanding cloud costs and tying them to business value. Monthly cloud spend (A) is a fundamental metric for overall cost visibility. Cost per user (B) and cost per workload (C) are crucial unit economic metrics that measure the business value and efficiency of cloud usage. Average server uptime (D), while a critical operational and reliability metric for Site Reliability Engineering (SRE) and IT Operations, is not a primary FinOps metric. FinOps is concerned with the cost of achieving a certain level of uptime, not the uptime percentage itself.

A. Monthly cloud spend: This is a foundational FinOps metric used to track overall expenditure and budget adherence, which is central to the Inform phase of the FinOps lifecycle.
B. Cost per user: This is a key unit cost metric that directly links cloud spending to business activity, helping to measure the value derived from cloud services.
C. Cost per workload: This metric is essential for allocating costs to specific applications or services, enabling engineering teams to understand and optimize their cloud consumption.

1. Storment, J.R., & Fuller, M. (2021). Cloud FinOps: Collaborative, Real-Time Cloud Financial Management (2nd ed.). O'Reilly Media.

Chapter 5, "Measuring Unit Costs": This chapter explicitly details the importance of unit economic metrics like cost per customer, cost per transaction, or cost per workload. It states, "The goal of establishing unit costs is to change the conversation from 'how much are we spending' to 'what is the cost to do X'." This supports options B and C as key FinOps metrics.

Chapter 4, "Understanding Cloud Usage and Cost": This chapter emphasizes the necessity of tracking overall spend as a primary step in the FinOps journey, validating option A. The book consistently frames metrics around cost and value, distinguishing them from purely operational metrics like uptime.

2. FinOps Foundation. (n.d.). What is FinOps?. FinOps Foundation.

"The Principles of FinOps" section: The principle "Business value of cloud drives decisions" highlights the need for metrics that connect cost to business outcomes. Metrics like cost per user or feature directly support this principle, while uptime is an operational measure, not a direct measure of business value from a financial perspective.

3. FinOps Foundation. (n.d.). FinOps Framework: Capabilities. FinOps Foundation.

"Measuring Unit Costs" Capability: This section describes the practice of "identifying a business metric and dividing it by the total cost of the cloud service... to produce a cost per [unit]." This directly validates the use of metrics like cost per user and cost per workload.

"Data Analysis and Showback" Capability: This capability focuses on providing visibility into cloud spending patterns, including total spend, which confirms the relevance of monthly cloud spend. The framework does not list operational metrics like uptime as a primary FinOps capability.