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
NAT gateway metrics can be found in the following locations in the Azure portal.
20
+
21
+
-**Metrics** page under **Monitoring** from a NAT gateway's resource page.
22
+
23
+
-**Insights** page under **Monitoring** from a NAT gateway's resource page.
24
+
25
+
:::image type="content" source="./media/nat-metrics/nat-insights-metrics.png" alt-text="Screenshot of the insights and metrics options in NAT gateway overview.":::
26
+
27
+
- Azure Monitor page under **Metrics**.
28
+
29
+
:::image type="content" source="./media/nat-metrics/azure-monitor.png" alt-text="Screenshot of the metrics section of Azure Monitor.":::
30
+
31
+
### Supported metrics for Microsoft.Network/natgateways
32
+
33
+
The following table lists the metrics available for the Microsoft.Network/natgateways resource type.
> Count aggregation is not recommended for any of the NAT gateway metrics. Count aggregation adds up the number of metric values and not the metric values themselves. Use Total aggregation instead to get the best representation of data values for connection count, bytes, and packets metrics.
41
+
>
42
+
> Use Average for best represented health data for the datapath availability metric.
43
+
>
44
+
> For information about aggregation types, see [aggregation types](/azure/azure-monitor/essentials/metrics-aggregation-explained#aggregation-types).
45
+
46
+
For more information, see [How to use NAT gateway metrics](nat-metrics.md#how-to-use-nat-gateway-metrics).
|Metric data|Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time.|[- Collected automatically at regular intervals.</br> - You can route some platform metrics to a Log Analytics workspace to query with other data. Check the **DS export** setting for each metric to see if you can use a diagnostic setting to route the metric data.]|[Metrics explorer](/azure/azure-monitor/essentials/metrics-getting-started)|[Azure NAT Gateway metrics supported by Azure Monitor](/azure/nat-gateway/monitor-nat-gateway-reference#metrics)|
23
+
|Resource log data|Logs are recorded system events with a timestamp. Logs can contain different types of data, and be structured or free-form text. You can route resource log data to Log Analytics workspaces for querying and analysis.|[Create a diagnostic setting](/azure/azure-monitor/essentials/create-diagnostic-settings) to collect and route resource log data.|[Log Analytics](/azure/azure-monitor/learn/quick-create-workspace)|[Azure NAT Gateway resource log data supported by Azure Monitor](/azure/nat-gateway/monitor-nat-gateway-reference#activity-log)|
24
+
|Activity log data|The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started.|- Collected automatically.</br> - [Create a diagnostic setting](/azure/azure-monitor/essentials/create-diagnostic-settings) to a Log Analytics workspace at no charge.|[Activity log](/azure/azure-monitor/essentials/activity-log)||
[Azure Monitor Network Insights](../network-watcher/network-insights-overview.md) allows you to visualize your Azure infrastructure setup and to review all metrics for your NAT gateway resource from a preconfigured metrics dashboard. These visual tools help you diagnose and troubleshoot any issues with your NAT gateway resource.
31
+
32
+
For more information on NAT Gateway Insights, see [Network Insights](nat-metrics.md#network-insights).
- See [Azure NAT Gateway monitoring data reference](monitor-nat-gateway-reference.md) for a reference of the metrics, logs, and other important values created for Azure NAT Gateway.
49
+
- See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for general details on monitoring Azure resources.
| Bytes | Bytes processed inbound and outbound | Sum |**Direction (In; Out)**, **Protocol (6 TCP; 17 UDP)**|
33
-
| Packets | Packets processed inbound and outbound | Sum |**Direction (In; Out)**, **Protocol (6 TCP; 17 UDP)**|
34
-
| Dropped Packets | Packets dropped by the NAT gateway | Sum | / |
35
-
| SNAT Connection Count | Number of new SNAT connections over a given interval of time | Sum |**Connection State (Attempted, Failed)**, **Protocol (6 TCP; 17 UDP)**|
36
-
| Total SNAT Connection Count | Total number of active SNAT connections | Sum |**Protocol (6 TCP; 17 UDP)**|
37
-
| Datapath Availability | Availability of the data path of the NAT gateway. Used to determine whether the NAT gateway endpoints are available for outbound traffic flow. | Avg |**Availability (0, 100)**|
> Count aggregation is not recommended for any of the NAT gateway metrics. Count aggregation adds up the number of metric values and not the metric values themselves. Use Sum aggregation instead to get the best representation of data values for connection count, bytes, and packets metrics.
@@ -77,7 +70,7 @@ The following sections detail how to use each NAT gateway metric to monitor, man
77
70
78
71
### Bytes
79
72
80
-
The **Bytes** metric shows you the amount of data going outbound through NAT gateway and returning inbound in response to an outbound connection.
73
+
The Bytes metric shows you the amount of data going outbound through NAT gateway and returning inbound in response to an outbound connection.
81
74
82
75
Use this metric to:
83
76
@@ -99,11 +92,11 @@ To view the amount of data passing through NAT gateway:
99
92
100
93
1. To see data processed inbound or outbound as their own individual lines in the metric graph, select **Apply splitting**.
101
94
102
-
1.In the **Values** drop-down menu, select **Direction (Out | In)**.
95
+
1. In the **Values** drop-down menu, select **Direction (Out | In)**.
103
96
104
97
### Packets
105
98
106
-
The packets metric shows you the number of data packets passing through NAT gateway.
99
+
The Packets metric shows you the number of data packets passing through NAT gateway.
107
100
108
101
Use this metric to:
109
102
@@ -113,9 +106,9 @@ Use this metric to:
113
106
114
107
To view the number of packets sent in one or both directions through NAT gateway, follow the same steps in the [Bytes](#bytes) section.
115
108
116
-
### Dropped packets
109
+
### Dropped Packets
117
110
118
-
The dropped packets metric shows you the number of data packets dropped by NAT gateway when traffic goes outbound or returns inbound in response to an outbound connection.
111
+
The Dropped Packets metric shows you the number of data packets dropped by NAT gateway when traffic goes outbound or returns inbound in response to an outbound connection.
119
112
120
113
Use this metric to:
121
114
@@ -127,9 +120,9 @@ Possible reasons for dropped packets:
127
120
128
121
- Outbound connectivity failure can cause packets to drop. Connectivity failure can happen for various reasons. See the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity) to help you further diagnose.
129
122
130
-
### SNAT connection count
123
+
### SNAT Connection Count
131
124
132
-
The SNAT connection count metric shows you the number of new SNAT connections within a specified time frame. This metric can be filtered by **Attempted** and **Failed** connection states. A failed connection volume greater than zero can indicate SNAT port exhaustion.
125
+
The SNAT Connection Count metric shows you the number of new SNAT connections within a specified time frame. This metric can be filtered by **Attempted** and **Failed** connection states. A failed connection volume greater than zero can indicate SNAT port exhaustion.
133
126
134
127
Use this metric to:
135
128
@@ -159,9 +152,9 @@ To view the connection state of your connections:
159
152
160
153
:::image type="content" source="./media/nat-metrics/nat-metrics-3.png" alt-text="Screenshot of the metrics configuration.":::
161
154
162
-
### Total SNAT connection count
155
+
### Total SNAT Connection Count
163
156
164
-
The **Total SNAT connection count** metric shows you the total number of active SNAT connections passing through NAT gateway.
157
+
The Total SNAT Connection Count metric shows you the total number of active SNAT connections passing through NAT gateway.
165
158
166
159
You can use this metric to:
167
160
@@ -178,7 +171,7 @@ Possible reasons for failed connections:
178
171
>[!NOTE]
179
172
> When NAT gateway is attached to a subnet and public IP address, the Azure platform verifies NAT gateway is healthy by conducting health checks. These health checks appear in NAT gateway's SNAT Connection Count metrics. The amount of health check related connections may vary as the health check service is optimized, but is negligible and doesn’t impact NAT gateway’s ability to connect outbound.
180
173
181
-
### Datapath availability
174
+
### Datapath Availability
182
175
183
176
The datapath availability metric measures the health of the NAT gateway resource over time. This metric indicates if NAT gateway is available for directing outbound traffic to the internet. This metric is a reflection of the health of the Azure infrastructure.
184
177
@@ -238,7 +231,7 @@ Setting the aggregation granularity to less than 5 minutes may trigger false pos
238
231
239
232
### Alerts for SNAT port exhaustion
240
233
241
-
Set up an alert on the **SNAT connection count** metric to notify you of connection failures on your NAT gateway. A failed connection volume greater than zero can indicate that you reached the connection limit on your NAT gateway or that you hit SNAT port exhaustion. Investigate further to determine the root cause of these failures.
234
+
Set up an alert on the **SNAT Connection Count** metric to notify you of connection failures on your NAT gateway. A failed connection volume greater than zero can indicate that you reached the connection limit on your NAT gateway or that you hit SNAT port exhaustion. Investigate further to determine the root cause of these failures.
242
235
243
236
To create the alert, use the following steps:
244
237
@@ -317,7 +310,7 @@ For more information on what each metric is showing you and how to analyze these
317
310
318
311
### What type of metrics are available for NAT gateway?
319
312
320
-
The NAT gateway supports [multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics). You can filter the multi-dimensional metrics by different dimensions to gain greater insight into the provided data. The [SNAT connection count](#snat-connection-count) metric allows you to filter the connections by Attempted and Failed connections, enabling you to distinguish between different types of connections made by the NAT gateway.
313
+
The NAT gateway supports [multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics). You can filter the multi-dimensional metrics by different dimensions to gain greater insight into the provided data. The [SNAT Connection Count](#snat-connection-count) metric allows you to filter the connections by Attempted and Failed connections, enabling you to distinguish between different types of connections made by the NAT gateway.
321
314
322
315
Refer to the dimensions column in the [metrics overview](#metrics-overview) table to see which dimensions are available for each NAT gateway metric.
0 commit comments