From 875cfefe7d143aca5258c625c98d87d3c95aba46 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Mon, 18 Sep 2023 09:44:11 -0600
Subject: [PATCH] Reduce restrictions on which metrics may be named utilization
 (#280)

---
 docs/general/metrics.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/general/metrics.md b/docs/general/metrics.md
index 938a5e73e..c4c6398fb 100644
--- a/docs/general/metrics.md
+++ b/docs/general/metrics.md
@@ -166,8 +166,10 @@ over all attribute values SHOULD be equal to the **limit**.
 
 - **utilization** - an instrument that measures the *fraction* of **usage**
 out of its **limit** should be called `entity.utilization`. For example,
-`system.memory.utilization` for the fraction of memory in use. Utilization
-values are in the range `[0, 1]`.
+`system.memory.utilization` for the fraction of memory in use. Utilization can
+be with respect to a fixed limit or a soft limit. Utilization values are
+represended as a ratio and are typically in the range `[0, 1]`, but may go above 1
+in case of exceeding a soft limit.
 
 - **time** - an instrument that measures passage of time should be called
 `entity.time`. For example, `system.cpu.time` with attribute `state = idle | user