Skip to content

Commit 456573c

Browse files
committedNov 17, 2020
added lightbox for images
1 parent 224b98d commit 456573c

11 files changed

+5
-5
lines changed
 

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Please check the [metrics documentation](./application-gateway-metrics.md) for t
2525
### Set your instance count based on your peak CPU usage
2626
If you are using a v1 SKU gateway, you’ll have the ability to set your Application Gateway up to 32 instances for scaling. Check your Application Gateway’s CPU utilization in the past one month for any spikes above 80%, it is available as a metric for you to monitor. It is recommended that you set your instance count according to your peak usage and with a 10% to 20% additional buffer to account for any traffic spikes.
2727

28-
:::image type="content" source="./media/application-gateway-covid-guidelines/v1-cpu-utilization.png" alt-text="V1 CPU utilization metrics":::
28+
:::image type="content" source="./media/application-gateway-covid-guidelines/v1-cpu-utilization-inline.png" alt-text="V1 CPU utilization metrics" lightbox="v1-cpu-utilization-exp.png":::
2929

3030
### Use the v2 SKU over v1 for its autoscaling capabilities and performance benefits
3131
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 TLS offload performance, quicker deployment and update times, zone redundancy, and more when compared to v1. For more information, see our [v2 documentation](./application-gateway-autoscaling-zone-redundant.md) and see our v1 to v2 [migration documentation](./migrate-v1-v2.md) to learn how to migrate your existing v1 SKU gateways to v2 SKU.
@@ -38,7 +38,7 @@ For Application Gateway v2 SKU, setting the maximum instance count to the maximu
3838

3939
Make sure to check your subnet size and available IP address count in your subnet and set your maximum instance count based on that. If your subnet doesn’t have enough space to accommodate, you will have to re-create your gateway in the same or different subnet which has enough capacity.
4040

41-
:::image type="content" source="./media/application-gateway-covid-guidelines/v2-autoscaling-max-instances.png" alt-text="V2 autoscaling configuration":::
41+
:::image type="content" source="./media/application-gateway-covid-guidelines/v2-autoscaling-max-instances-inline.png" alt-text="V2 autoscaling configuration" lightbox="v2-autoscaling-max-instances-exp.png":::
4242

4343
### Set your minimum instance count based on your average Compute Unit usage
4444

@@ -48,7 +48,7 @@ It is recommended that you set your minimum instance count to an optimal level.
4848

4949
Check your Compute Unit metric for the past one month. Compute unit metric is a representation of your gateway's CPU utilization and based on your peak usage divided by 10, you can set the minimum number of instances required. Note that 1 application gateway instance can handle a minimum of 10 compute units
5050

51-
:::image type="content" source="./media/application-gateway-covid-guidelines/compute-unit-metrics.png" alt-text="V2 compute unit metrics":::
51+
:::image type="content" source="./media/application-gateway-covid-guidelines/compute-unit-metrics-inline.png" alt-text="V2 compute unit metrics" lightbox="compute-unit-metrics-exp.png":::
5252

5353
## Manual scaling for Application Gateway v2 SKU (Standard_v2/WAF_v2)
5454

@@ -89,7 +89,7 @@ This example shows you how to use the Azure portal to set up an alert when the f
8989
4. Click on **New alert rule** and define your condition and actions
9090
5. Click on **Create alert rule** to create and enable the alert
9191

92-
:::image type="content" source="./media/application-gateway-covid-guidelines/create-alerts.png" alt-text="V2 create alerts":::
92+
:::image type="content" source="./media/application-gateway-covid-guidelines/create-alerts-inline.png" alt-text="V2 create alerts" lightbox="create-alerts-exp.png":::
9393

9494
## Alerts for Application Gateway v2 SKU (Standard_v2/WAF_v2)
9595

@@ -105,7 +105,7 @@ This example shows you how to use the Azure portal to set up an alert when 75% o
105105
3. Add a metric for **Average Current Compute Units**.
106106
4. If you've set your minimum instance count to be your average CU usage, go ahead and set an alert when 75% of your minimum instances are in use. For example, if your average usage is 10 CUs, set an alert on 7.5 CUs. This alerts you if usage is increasing and gives you time to respond. You can raise the minimum if you think this traffic will be sustained to alert you that traffic may be increasing.
107107

108-
:::image type="content" source="./media/application-gateway-covid-guidelines/compute-unit-alert.png" alt-text="V2 compute unit alerts":::
108+
:::image type="content" source="./media/application-gateway-covid-guidelines/compute-unit-alert-inline.png" alt-text="V2 compute unit alerts" lightbox="compute-unit-alert-exp.png":::
109109

110110
> [!NOTE]
111111
> You can set the alert to occur at a lower or higher CU utilization percentage depending on how sensitive you want to be to potential traffic spikes.

0 commit comments

Comments
 (0)
Please sign in to comment.