Skip to content

Commit 55059a1

Browse files
mikebudzynskimikebudzynski
authored
Merge pull request #1 from jijohn14/patch-1
Minor suggestions
2 parents 657c112 + a6c5cda commit 55059a1

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

‎articles/api-management/api-management-howto-autoscale.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.author: apimpm
1717

1818
# Automatically scale an Azure API Management instance
1919

20-
Azure API Management service instance can scale automatically based on a set of rules. This behavior can be enabled and configured through Azure Monitor and is supported in **Standard** and **Premium** tiers of the Azure API Management service.
20+
Azure API Management service instance can scale automatically based on a set of rules. This behavior can be enabled and configured through Azure Monitor and is supported only in **Standard** and **Premium** tiers of the Azure API Management service.
2121

2222
The article walks through the process of configuring autoscale and suggests optimal configuration of autoscale rules.
2323

@@ -36,13 +36,13 @@ Certain limitations and consequences of scaling decisions need to be considered
3636

3737
+ Autoscale can be enabled only for **Standard** and **Premium** tiers of Azure API Management service.
3838
+ Pricing tiers also specify the maximum number of units for a service instance.
39-
+ Scaling process will take at least 20 minutes. If the service instance is locked by another operation, the process will take longer.
40-
+ In case of multiregional deployments, only units in the **Primary location** can be scaled. Units in secondary locations can't be scaled.
41-
+ Scaling will trigger a restart of the Azure API Management units, which can cause an intermittent performance degradation.
39+
+ Scaling process will take at least 20 minutes.
40+
+ If the service is locked by another operation, scaling request will fail and retry automatically.
41+
+ In case of a service with multi-regional deployments, only units in the **Primary location** can be scaled. Units in other locations can't be scaled.
4242

43-
## Enable and configure autoscale for Azure API Management instance
43+
## Enable and configure autoscale for Azure API Management service
4444

45-
Follow the steps below to configure autoscale behavior for an Azure API Management instance.
45+
Follow the steps below to configure autoscale for an Azure API Management service:
4646

4747
1. Navigate to **Monitor** instance in the Azure portal.
4848

@@ -52,8 +52,8 @@ Follow the steps below to configure autoscale behavior for an Azure API Manageme
5252

5353
![Azure Monitor autoscale resource](media/api-management-howto-autoscale/02.png)
5454

55-
3. Specify location of your Azure API Management instance in the dropdown menus.
56-
4. Click on the Azure API Management instance.
55+
3. Locate your Azure API Management service based on the filters in dropdown menus.
56+
4. Select the desired Azure API Management service instance.
5757
5. In the newly opened section, click the **Enable autoscale** button.
5858

5959
![Azure Monitor autoscale enable](media/api-management-howto-autoscale/03.png)
@@ -101,7 +101,7 @@ Follow the steps below to configure autoscale behavior for an Azure API Manageme
101101
| Metric name | Capacity | Same metric as the one used for the scale out rule. |
102102
| Time grain statistic | Average | |
103103
| Operator | Less than | |
104-
| Threshold | 35% | Similarly to the scale out rule, this value heavily depends on the usage patterns of the Azure API Management. <br /> Ideally, it should be lower than half of the value used for scale out purposes. For example, if 80% was used for the scale out rule and Azure API Management instance has scaled out from 1 to 2 units, the new average capacity metric value might drop to around 80% / 2 = 40%. To avoid constant deadlock between scaling out and in, 35% could be a reasonable threshold. |
104+
| Threshold | 35% | Similarly to the scale out rule, this value heavily depends on the usage patterns of the Azure API Management. |
105105
| Duration (in minutes) | 30 | Same value as the one used for the scale out rule. |
106106
| *Action* | | |
107107
| Operation | Decrease count by | Opposite to what was used for the scale out rule. |
@@ -115,7 +115,7 @@ Follow the steps below to configure autoscale behavior for an Azure API Manageme
115115
12. Set the **maximum** number of Azure API Management units.
116116

117117
> [!NOTE]
118-
> Azure API Management tiers enforce a limit of units an instance can scale out to.
118+
> Azure API Management has a limit of units an instance can scale out to. The limit depends on a service tier.
119119
120120
![Azure Monitor scale in rule](media/api-management-howto-autoscale/07.png)
121121

@@ -124,4 +124,3 @@ Follow the steps below to configure autoscale behavior for an Azure API Manageme
124124
## Next steps
125125

126126
+ [How to deploy an Azure API Management service instance to multiple Azure regions](api-management-howto-deploy-multi-region.md)
127-
+ [How to automatically scale an Azure API Management service instance](api-management-howto-autoscale.md)

0 commit comments

Comments
 (0)