Skip to content

Commit c3e79fb

Browse files
committed
fine tune intro
1 parent 0f7a07e commit c3e79fb

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

articles/application-gateway/high-traffic-support.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,23 +11,26 @@ ms.author: caya
1111

1212
# Application Gateway high traffic support
1313

14-
This article describes a few suggested guidelines to help you set up your Application Gateway to handle extra traffic due to high traffic volume scenarios. You can use Application Gateway with Web Application Firewall (WAF) for a scalable and secure way to manage traffic to your web applications.
14+
This article describes a few suggested guidelines to help you set up your Application Gateway to handle extra traffic due to high traffic volume scenarios, such as the COVID-19 situation. You can use Application Gateway with Web Application Firewall (WAF) for a scalable and secure way to manage traffic to your web applications.
1515

1616
The following suggestions help you set up Application Gateway with WAF to handle extra traffic.
1717

1818
## Use the v2 SKU over v1 for its autoscaling capabilities and performance benefits
1919
The v2 SKU offers autoscaling to ensure that your Application Gateway can scale up as traffic increases. It also offers other significant performance benefits, such as 5x better SSL offload performance, quicker deployment and update times, zone redundancy, and more when compared to v1. For more information, see our [v2 documentation](https://docs.microsoft.com/azure/application-gateway/application-gateway-autoscaling-zone-redundant).
2020

21-
## Set maximum instance count to the maximum possible (125)
21+
## Set maximum instance count to the maximum possible (125)
22+
2223
Assuming you have an Application Gateway v2 SKU, setting the maximum instance count to the maximum possible value of 125 allows the Application Gateway to scale out as needed. This allows it to handle the possible increase in traffic to your applications. You will only be charged for the Capacity Units (CUs) you use.
2324

24-
## Set your minimum instance count based on your average CU usage
25+
## Set your minimum instance count based on your average CU usage
26+
2527
Assuming you have an Application Gateway v2 SKU, autoscaling takes six to seven minutes to scale out. With a higher minimum instance count, the Application Gateway can better handle your traffic when the load is increased, because a spike in traffic doesn't require an autoscaling operation.
2628

2729
## Alert if a certain metric surpasses 75% of average CU utilization
2830
See the [Application Gateway Metrics documentation](https://docs.microsoft.com/azure/application-gateway/application-gateway-metrics#metrics-visualization) for a detailed explanation of our metrics and other walkthroughs.
2931

3032
### Example: Setting up an alert on 75% of average CU usage
33+
3134
This example shows you how to use the Azure portal to set up an alert when 75% of average CU usage is reached.
3235
1. Navigate to your **Application Gateway**.
3336
2. On the left panel, select **Metrics** under the **Monitoring** tab.
@@ -45,6 +48,7 @@ If you want an extra layer of security in front of your application, use the App
4548
Enable bot protection to block known bad bots. This should reduce the amount of traffic getting to your application. For more information, see [bot protection with set up instructions](https://docs.microsoft.com/azure/web-application-firewall/ag/configure-waf-custom-rules).
4649

4750
## Turn on diagnostics on Application Gateway and WAF
51+
4852
Diagnostic logs allow you to view firewall logs, performance logs, and access logs. You can use these logs in Azure to manage and troubleshoot Application Gateways. For more information, see our [diagnostics documentation](https://docs.microsoft.com/azure/application-gateway/application-gateway-diagnostics#diagnostic-logging).
4953

5054
## Set up an SSL policy for extra security

articles/application-gateway/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@
5050
href: application-gateway-components.md
5151
- name: Configuration overview
5252
href: configuration-overview.md
53-
- name: High trafic support
53+
- name: High traffic support
5454
href: high-traffic-support.md
5555
- name: Autoscaling v2 SKU
5656
href: application-gateway-autoscaling-zone-redundant.md

0 commit comments

Comments
 (0)