Skip to content

Commit 15d4f23

Browse files
committed
changed image directory + updated article
1 parent 926637b commit 15d4f23

File tree

12 files changed

+31
-34
lines changed

12 files changed

+31
-34
lines changed
Lines changed: 31 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,29 @@
11
---
22
title: Azure Monitor metrics for Application Gateway
3-
description: Learn how to use metrics to monitor performance of application gateway
3+
description: Monitor Application Gateway performance with Azure Monitor metrics including backend connect time, response latency, and WAF data. Configure alerts and visualize metric trends.
4+
#customer intent: As a cloud administrator, I want to understand Application Gateway timing metrics so that I can diagnose performance issues between my application gateway and backend servers.
45
services: application-gateway
56
author: mbender-ms
67
ms.service: azure-application-gateway
78
ms.topic: concept-article
8-
ms.date: 06/17/2024
9+
ms.date: 06/11/2025
910
ms.author: mbender
10-
11+
ms.custom:
12+
- ai-gen-docs-bap
13+
- ai-gen-description
14+
- ai-seo-date:06/11/2025
1115
---
16+
1217
# Metrics for Application Gateway
1318

14-
Application Gateway publishes data points to [Azure Monitor](/azure/azure-monitor/overview) for the performance of your Application Gateway and backend instances. These data points are called metrics, and are numerical values in an ordered set of time-series data. Metrics describe some aspect of your application gateway at a particular time. If there are requests flowing through the Application Gateway, it measures and sends its metrics in 60-second intervals. If there are no requests flowing through the Application Gateway or no data for a metric, the metric isn't reported. For more information, see [Azure Monitor metrics](/azure/azure-monitor/essentials/data-platform-metrics).
19+
Azure Application Gateway provides comprehensive monitoring capabilities through [Azure Monitor](/azure/azure-monitor/overview) metrics. These metrics help you track the performance and health of your application gateway instance, including request latency, backend connectivity, and throughput measurements.
20+
21+
This article describes the metrics available for Application Gateway, how to access and visualize them, and how to configure alerts based on metric thresholds. You'll learn about timing metrics that help diagnose performance bottlenecks, backend health indicators, and Web Application Firewall (WAF) metrics for security monitoring. For more information, see [Azure Monitor metrics](/azure/azure-monitor/essentials/data-platform-metrics).
22+
23+
24+
## Metrics overview
1525

16-
<a name="metrics-supported-by-application-gateway-v1-sku"></a>
26+
Application Gateway metrics are numerical values collected at regular intervals that describe the performance characteristics of your gateway at specific points in time. These metrics are automatically published to Azure Monitor when requests flow through your Application Gateway, with data points captured every 60 seconds.
1727

1828
## Metrics supported by Application Gateway V2 SKU
1929

@@ -24,17 +34,15 @@ Application Gateway publishes data points to [Azure Monitor](/azure/azure-monito
2434

2535
Application Gateway provides several built‑in timing metrics related to the request and response, which are all measured in milliseconds.
2636

27-
:::image type="content" source="./media/application-gateway-metrics/application-gateway-metrics.png" alt-text="[Diagram of timing metrics for the Application Gateway" border="false":::
37+
:::image type="content" source="./media/application-gateway-metrics/application-gateway-metrics.png" alt-text="Screenshot of diagram showing timing metrics for the Application Gateway.":::
2838

2939
> [!NOTE]
30-
>
31-
> If there is more than one listener in the Application Gateway, then always filter by *Listener* dimension while comparing different latency metrics in order to get meaningful inference.
40+
> If there's more than one listener in the Application Gateway, then always filter by *Listener* dimension while comparing different latency metrics in order to get meaningful inference.
3241
3342
> [!NOTE]
34-
>
35-
> Latency might be observed in the metric data, as all metrics are aggregated at one-minute intervals. This latency may vary for different application gateway instances based on the metric start time.
43+
> Latency might be observed in the metric data, as all metrics are aggregated at one-minute intervals. This latency can vary for different application gateway instances based on the metric start time.
3644
37-
You can use timing metrics to determine whether the observed slowdown is due to the client network, Application Gateway performance, the backend network and backend server TCP stack saturation, backend application performance, or large file size. For more information, see [Timing metrics](monitor-application-gateway-reference.md#timing-metrics-for-application-gateway-v2-sku).
45+
You can use timing metrics to determine whether the observed slowdown is due to the client network, Application Gateway performance, the backend network, and backend server TCP stack saturation, backend application performance, or large file size. For more information, see [Timing metrics](monitor-application-gateway-reference.md#timing-metrics-for-application-gateway-v2-sku).
3846

3947
For example, if there's a spike in *Backend first byte response time* trend but the *Backend connect time* trend is stable, you can infer that the application gateway to backend latency and the time taken to establish the connection is stable. The spike is caused due to an increase in the response time of backend application. On the other hand, if the spike in *Backend first byte response time* is associated with a corresponding spike in *Backend connect time*, you can deduce that either the network between Application Gateway and backend server or the backend server TCP stack has saturated.
4048

@@ -60,7 +68,7 @@ Browse to an application gateway, under **Monitoring** select **Metrics**. To vi
6068

6169
In the following image, you see an example with three metrics displayed for the last 30 minutes:
6270

63-
:::image type="content" source="media/application-gateway-diagnostics/figure5.png" alt-text="Screenshot shows the Metric view of three metrics." lightbox="media/application-gateway-diagnostics/figure5-lb.png":::
71+
:::image type="content" source="media/application-gateway-metrics/figure5.png" alt-text="Screenshot of the Metric view displaying three metrics." lightbox="media/application-gateway-metrics/figure5.png":::
6472

6573
To see a current list of metrics, see [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metrics-supported).
6674

@@ -72,43 +80,32 @@ The following example walks you through creating an alert rule that sends an ema
7280

7381
1. select **Add metric alert** to open the **Add rule** page. You can also reach this page from the metrics page.
7482

75-
!["Add metric alert" button][6]
83+
:::image type="content" source="./media/application-gateway-metrics/figure6.png" alt-text="Screenshot of the Add metric alert button.":::
7684

77-
2. On the **Add rule** page, fill out the name, condition, and notify sections, and select **OK**.
85+
1. On the **Add rule** page, fill out the name, condition, and notify sections, and select **OK**.
7886

79-
* In the **Condition** selector, select one of the four values: **Greater than**, **Greater than or equal**, **Less than**, or **Less than or equal to**.
87+
- In the **Condition** selector, select one of the four values: **Greater than**, **Greater than or equal**, **Less than**, or **Less than or equal to**.
8088

81-
* In the **Period** selector, select a period from five minutes to six hours.
89+
- In the **Period** selector, select a period from five minutes to six hours.
8290

83-
* If you select **Email owners, contributors, and readers**, the email can be dynamic, based on the users who have access to that resource. Otherwise, you can provide a comma-separated list of users in the **Additional administrator email(s)** box.
91+
- If you select **Email owners, contributors, and readers**, the email can be dynamic, based on the users who have access to that resource. Otherwise, you can provide a comma-separated list of users in the **Additional administrator email(s)** box.
8492

85-
![Add rule page][7]
93+
:::image type="content" source="./media/application-gateway-metrics/figure7.png" alt-text="Screenshot of the Add rule page.":::
8694

8795
If the threshold is breached, an email that's similar to the one in the following image arrives:
8896

89-
![Email for breached threshold][8]
97+
:::image type="content" source="./media/application-gateway-metrics/figure8.png" alt-text="Screenshot of email notification for breached threshold.":::
9098

9199
A list of alerts appears after you create a metric alert. It provides an overview of all the alert rules.
92100

93-
![List of alerts and rules][9]
101+
:::image type="content" source="./media/application-gateway-metrics/figure9.png" alt-text="Screenshot showing list of alerts and rules.":::
94102

95103
To learn more about alert notifications, see [Receive alert notifications](/azure/azure-monitor/alerts/alerts-overview).
96104

97105
To understand more about webhooks and how you can use them with alerts, visit [Configure a webhook on an Azure metric alert](/azure/azure-monitor/alerts/alerts-webhooks).
98106

99107
## Next steps
100108

101-
* Visualize counter and event logs by using [Azure Monitor logs](/previous-versions/azure/azure-monitor/insights/azure-networking-analytics).
102-
* [Visualize your Azure activity log with Power BI](https://powerbi.microsoft.com/blog/monitor-azure-audit-logs-with-power-bi/) blog post.
103-
* [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.
104-
105-
[1]: ./media/application-gateway-diagnostics/figure1.png
106-
[2]: ./media/application-gateway-diagnostics/figure2.png
107-
[3]: ./media/application-gateway-diagnostics/figure3.png
108-
[4]: ./media/application-gateway-diagnostics/figure4.png
109-
[5]: ./media/application-gateway-diagnostics/figure5.png
110-
[6]: ./media/application-gateway-diagnostics/figure6.png
111-
[7]: ./media/application-gateway-diagnostics/figure7.png
112-
[8]: ./media/application-gateway-diagnostics/figure8.png
113-
[9]: ./media/application-gateway-diagnostics/figure9.png
114-
[10]: ./media/application-gateway-diagnostics/figure10.png
109+
- Visualize counter and event logs by using [Azure Monitor logs](/previous-versions/azure/azure-monitor/insights/azure-networking-analytics).
110+
- [Visualize your Azure activity log with Power BI](https://powerbi.microsoft.com/blog/monitor-azure-audit-logs-with-power-bi/) blog post.
111+
- [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.
72.1 KB
Loading
39.5 KB
Loading
25.4 KB
Loading
15.8 KB
Loading
33.7 KB
Loading
71.9 KB
Loading
56.6 KB
Loading
93.1 KB
Loading
67.7 KB
Loading

0 commit comments

Comments
 (0)