Update api-management-availability-capacity.md

tehnoonr · web-flow · commit 0bb7e4a3ca89 · 2025-07-16T14:29:04.000-05:00
Adjusted threshold for max capacity spikes
diff --git a/includes/api-management-availability-capacity.md b/includes/api-management-availability-capacity.md
@@ -8,4 +8,4 @@ ms.author: danlep
 
 
 > [!IMPORTANT]
-> The **Max** aggregation of the capacity metric is only supported in the **Premium** tier of API Management. This aggregation is intended for informational purposes only and should not be used for scaling decisions or alerting. Short-lived spikes in **Max** capacity are expected and typically not a cause for concern. However, if these spikes persist for 10 minutes or longer, further investigation may be warranted. For more infromation, refer to [Use capacity for scaling decisions](../articles/api-management/api-management-capacity.md#use-capacity-for-scaling-decisions) mentioned later in this document.
+> The **Max** aggregation of the capacity metric is only supported in the **Premium** tier of API Management. This aggregation is intended for informational purposes only and should not be used for scaling decisions or alerting. Short-lived spikes in **Max** capacity are expected and typically not a cause for concern. However, if these spikes persist for 15 consecutive minutes or longer, further investigation may be warranted. For more infromation, refer to [Use capacity for scaling decisions](../articles/api-management/api-management-capacity.md#use-capacity-for-scaling-decisions) mentioned later in this document.

Original file line number	Diff line number	Diff line change
`@@ -8,4 +8,4 @@ ms.author: danlep`
`8`	`8`
`9`	`9`
`10`	`10`	`> [!IMPORTANT]`
`11`		-> The Max aggregation of the capacity metric is only supported in the Premium tier of API Management. This aggregation is intended for informational purposes only and should not be used for scaling decisions or alerting. Short-lived spikes in Max capacity are expected and typically not a cause for concern. However, if these spikes persist for 10 minutes or longer, further investigation may be warranted. For more infromation, refer to [Use capacity for scaling decisions](../articles/api-management/api-management-capacity.md#use-capacity-for-scaling-decisions) mentioned later in this document.
	`11`	+> The Max aggregation of the capacity metric is only supported in the Premium tier of API Management. This aggregation is intended for informational purposes only and should not be used for scaling decisions or alerting. Short-lived spikes in Max capacity are expected and typically not a cause for concern. However, if these spikes persist for 15 consecutive minutes or longer, further investigation may be warranted. For more infromation, refer to [Use capacity for scaling decisions](../articles/api-management/api-management-capacity.md#use-capacity-for-scaling-decisions) mentioned later in this document.