Skip to content

Commit fa62e84

Browse files
authored
Update api-management-capacity.md
Added reference to the changed capacity metric and also added additional guidance around how to use capacity metric for scaling decisions.
1 parent 661bab7 commit fa62e84

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/api-management/api-management-capacity.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,8 @@ Available aggregations for these metrics are as follows.
5656

5757
In the Developer, Basic, Standard, and Premium tiers, the **Capacity** metric is available for making decisions about scaling or upgrading an API Management instance. Its construction is complex and imposes certain behavior.
5858

59+
[!INCLUDE [capacity-change.md](../../includes/api-management-capacity-change.md)]
60+
5961
Available aggregations for this metric are as follows.
6062

6163
* **Avg** - Average percentage of capacity used across gateway processes in every [unit](upgrade-and-scale.md) of an API Management instance.
@@ -171,6 +173,7 @@ Use capacity metrics for making decisions whether to scale an API Management ins
171173
+ Ignore sudden spikes that are most likely not related to an increase in load (see [Capacity metric behavior](#capacity-metric-behavior) section for explanation).
172174
+ As a general rule, upgrade or scale your instance when a capacity metric value exceeds **60% - 70%** for a long period of time (for example, 30 minutes). Different values may work better for your service or scenario.
173175
+ If your instance or workspace gateway is configured with only 1 unit, upgrade or scale it when a capacity metric value exceeds **40%** for a long period. This recommendation is based on the need to reserve capacity for guest OS updates in the underlying service platform.
176+
+ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric.
174177

175178
> [!TIP]
176179
> If you are able to estimate your traffic beforehand, test your API Management instance or workspace gateway on workloads you expect. You can increase the request load gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.

0 commit comments

Comments
 (0)