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
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.
4
5
services: application-gateway
5
6
author: mbender-ms
6
7
ms.service: azure-application-gateway
7
8
ms.topic: concept-article
8
-
ms.date: 06/17/2024
9
+
ms.date: 06/11/2025
9
10
ms.author: mbender
10
-
11
+
ms.custom:
12
+
- ai-gen-docs-bap
13
+
- ai-gen-description
14
+
- ai-seo-date:06/11/2025
11
15
---
16
+
12
17
# Metrics for Application Gateway
13
18
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).
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.
17
27
18
28
## Metrics supported by Application Gateway V2 SKU
19
29
@@ -24,17 +34,15 @@ Application Gateway publishes data points to [Azure Monitor](/azure/azure-monito
24
34
25
35
Application Gateway provides several built‑in timing metrics related to the request and response, which are all measured in milliseconds.
26
36
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.":::
28
38
29
39
> [!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.
32
41
33
42
> [!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.
36
44
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).
38
46
39
47
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.
40
48
@@ -60,7 +68,7 @@ Browse to an application gateway, under **Monitoring** select **Metrics**. To vi
60
68
61
69
In the following image, you see an example with three metrics displayed for the last 30 minutes:
62
70
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":::
64
72
65
73
To see a current list of metrics, see [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metrics-supported).
66
74
@@ -72,43 +80,32 @@ The following example walks you through creating an alert rule that sends an ema
72
80
73
81
1. select **Add metric alert** to open the **Add rule** page. You can also reach this page from the metrics page.
74
82
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.":::
76
84
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**.
78
86
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**.
80
88
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.
82
90
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.
84
92
85
-
![Add rule page][7]
93
+
:::image type="content" source="./media/application-gateway-metrics/figure7.png" alt-text="Screenshot of the Add rule page.":::
86
94
87
95
If the threshold is breached, an email that's similar to the one in the following image arrives:
88
96
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.":::
90
98
91
99
A list of alerts appears after you create a metric alert. It provides an overview of all the alert rules.
92
100
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.":::
94
102
95
103
To learn more about alert notifications, see [Receive alert notifications](/azure/azure-monitor/alerts/alerts-overview).
96
104
97
105
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).
98
106
99
107
## Next steps
100
108
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.
0 commit comments