Skip to content

Commit 5e343d5

Browse files
Merge pull request #265850 from MJyot/v1-migration
scheduled autoscale updates
2 parents 3248bfa + 247285b commit 5e343d5

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ For those experiencing predictable daily traffic patterns and who have a reliabl
1818

1919
While autoscaling is commonly utilized, it’s important to note that Application Gateway doesn't currently support prescheduled capacity adjustments natively.
2020

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.
2222

2323
## Set up scheduled autoscaling
2424

@@ -28,7 +28,7 @@ To implement scheduled autoscaling:
2828
3. Create PowerShell runbooks for increasing and decreasing min autoscaling capacity for the Application Gateway resource.
2929
4. Create the schedules during which the runbooks need to be implemented.
3030
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.
3232

3333
## Configure automation
3434

@@ -73,7 +73,12 @@ Next, create the following two schedules:
7373
| --- | --- |
7474
|IncreaseMin | Falls back on native autoscaling. Next run of DecreaseMin should be no-op as the count doesn’t need to be adjusted. |
7575
|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?
7678

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+
7782
> [!NOTE]
7883
> Send email to [email protected] if you have questions or need help to set up managed and scheduled autoscale for your deployments.
7984

0 commit comments

Comments
 (0)