Skip to content

Commit c7acc4e

Browse files
authored
Update api-management-availability-capacity.md
Adding clarification about usage of Max Capacity.
1 parent d461132 commit c7acc4e

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

includes/api-management-availability-capacity.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,4 @@ ms.author: danlep
88

99

1010
> [!IMPORTANT]
11-
> The **Max** aggregation of the capacity metric is only supported in the **Premium** tier of API Management.
12-
>
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.

0 commit comments

Comments
 (0)