You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ For those experiencing predictable daily traffic patterns and who have a reliabl
18
18
19
19
While autoscaling is commonly utilized, it’s important to note that Application Gateway doesn't currently support prescheduled capacity adjustments natively.
20
20
21
-
The goal is to use Azure Automation to create a schedule for running runbooks that adjust the minimum autoscaling capacity of Application Gateway to meet traffic demands.
21
+
The goal is to use Azure Automation to create a schedule for running runbooks that adjust the minimum autoscaling capacity of Application Gateway to meet traffic demands during peak vs non peak hours.
22
22
23
23
## Set up scheduled autoscaling
24
24
@@ -28,7 +28,7 @@ To implement scheduled autoscaling:
28
28
3. Create PowerShell runbooks for increasing and decreasing min autoscaling capacity for the Application Gateway resource.
29
29
4. Create the schedules during which the runbooks need to be implemented.
30
30
5. Associate the runbooks with their respective schedules.
31
-
6. Associate the system assigned managed identity noted in step 2 with the Application Gateway resource.
31
+
6. Associate the system assigned managed identity noted in step 2 with the Application Gateway and Application Gateway VNET resource.
32
32
33
33
## Configure automation
34
34
@@ -73,7 +73,12 @@ Next, create the following two schedules:
73
73
| --- | --- |
74
74
|IncreaseMin | Falls back on native autoscaling. Next run of DecreaseMin should be no-op as the count doesn’t need to be adjusted. |
75
75
|DecreaseMin | Additional cost to the customer for the (unintended) capacity that is provisioned for those hours. Next run of IncreaseMin should be no-op because the count doesn’t need to be adjusted. |
76
+
77
+
- Can the autoscale configurations be changed multiple times per day?
76
78
79
+
Frequent adjustments to autoscale configurations are not advised. For optimal balance, consider scheduling updates twice
80
+
daily to coincide with peak and non-peak usage pattern.
81
+
77
82
> [!NOTE]
78
83
> Send email to [email protected] if you have questions or need help to set up managed and scheduled autoscale for your deployments.
0 commit comments