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
Copy file name to clipboardExpand all lines: articles/virtual-wan/monitor-virtual-wan-reference.md
+24-2Lines changed: 24 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Monitoring data reference for Azure Virtual WAN
3
3
description: This article contains important reference material you need when you monitor Azure Virtual WAN by using Azure Monitor.
4
-
ms.date: 07/25/2024
4
+
ms.date: 08/28/2024
5
5
ms.custom: horz-monitor
6
6
ms.topic: reference
7
7
author: cherylmc
@@ -28,7 +28,7 @@ This table contains more information about some of the metrics in the preceding
28
28
29
29
| Metric | Description |
30
30
|:-------|:------------|
31
-
|**Data Processed by the Virtual Hub Router**| Data on how much traffic traverses the virtual hub router in a given time period. Only the following flows use the virtual hub router: virtual network to virtual network, same hub and interhub, and VPN/ExpressRoute branch to virtual network, for interhub. If a virtual hub is secured with routing intent, then these flows traverse the firewall instead of the hub router. |
31
+
|**Data Processed by the Virtual Hub Router**| Data on how much traffic traverses the virtual hub router in a given time period. Only the following flows use the virtual hub router: virtual network to virtual network, same hub and interhub, and VPN/ExpressRoute branch to virtual network, for interhub. If a virtual hub is secured with routing intent, then these flows traverse the firewall instead of the hub router. *Same hub* and *interhub* refer to virtual network to virtual network traffic. These were previously described as *VNet to VNet* for *same hub and interhub* and *VPN/ExpressRoute branch to VNet* for *interhub*.|
32
32
| **Routing Infrastructure Units** | The virtual hub's routing infrastructure units (RIU). The virtual hub's RIU determines how much bandwidth the virtual hub router can process for flows traversing the virtual hub router. The hub's RIU also determines how many VMs in spoke VNets the virtual hub router can support. For more information on routing infrastructure units, see [Virtual Hub Capacity](hub-settings.md#capacity).
33
33
|**Spoke VM Utilization**| The approximate number of deployed spoke VMs as a percentage of the total number of spoke VMs that the hub's routing infrastructure units can support. For example, if the hub's RIU is set to 2, which supports 2,000 spoke VMs, and 1,000 VMs are deployed across spoke virtual networks, this metric's value is approximately 50%. |
34
34
@@ -187,6 +187,28 @@ This table contains more information about the preceding table.
187
187
|**Route Diagnostic Logs**| Logs related to events for static routes, BGP, route updates, and other diagnostics. |
188
188
|**IKE Diagnostic Logs**| IKE-specific diagnostics for IPsec connections. |
189
189
190
+
### Log Analytics sample query
191
+
192
+
If you selected to send diagnostic data to a Log Analytics Workspace, then you can use SQL-like queries, such as the following example, to examine the data. For more information, see [Log Analytics Query Language](/services-hub/health/log-analytics-query-language).
193
+
194
+
The following example contains a query to obtain site-to-site route diagnostics.
195
+
196
+
`AzureDiagnostics | where Category == "RouteDiagnosticLog"`
197
+
198
+
Replace the following values, after the `==`, as needed based on the tables in this article.
199
+
200
+
- GatewayDiagnosticLog
201
+
- IKEDiagnosticLog
202
+
- P2SDiagnosticLog
203
+
- TunnelDiagnosticLog
204
+
- RouteDiagnosticLog
205
+
206
+
In order to run the query, you have to open the Log Analytics resource you configured to receive the diagnostic logs, and then select **Logs** under the **General** tab on the left side of the pane:
207
+
208
+
:::image type="content" source="./media/monitor-virtual-wan-reference/log-analytics-query-samples.png" alt-text="Screenshot of Log Analytics Query samples." lightbox="./media/monitor-virtual-wan-reference/log-analytics-query-samples.png":::
209
+
210
+
For Azure Firewall, a [workbook](../firewall/firewall-workbook.md) is provided to make log analysis easier. Using its graphical interface, you can investigate the diagnostic data without manually writing any Log Analytics query.
Virtual WAN uses Network Insights to provide users and operators with the ability to view the state and status of a virtual WAN, presented through an autodiscovered topological map. Resource state and status overlays on the map give you a snapshot view of the overall health of the virtual WAN. You can navigate resources on the map by using one-click access to the resource configuration pages of the Virtual WAN portal. For more information, see [Azure Monitor Network Insights for Virtual WAN](azure-monitor-insights.md).
18
+
Virtual WAN uses Network Insights to provide users and operators with the ability to view the state and status of a Virtual WAN, presented through an autodiscovered topological map. Resource state and status overlays on the map give you a snapshot view of the overall health of the Virtual WAN. You can navigate resources on the map by using one-click access to the resource configuration pages of the Virtual WAN portal. For more information, see [Azure Monitor Network Insights for Virtual WAN](azure-monitor-insights.md).
You can view metrics for Virtual WAN by using the Azure portal.
37
-
38
-
The following steps help you locate and view metrics:
32
+
You can view metrics for Virtual WAN by using the Azure portal. The following steps help you locate and view metrics:
39
33
40
-
Select **Monitor Gateway** and then **Metrics**. You can also select **Metrics** at the bottom to view a dashboard of the most important metrics for site-to-site and point-to-site VPN.
34
+
1.Select **Monitor Gateway** and then **Metrics**. You can also select **Metrics** at the bottom to view a dashboard of the most important metrics for site-to-site and point-to-site VPN.
On the **Metrics** page, you can view the metrics.
38
+
1.On the **Metrics** page, you can view the metrics.
45
39
46
-
:::image type="content" source="./media/monitor-virtual-wan-reference/metrics-page.png" alt-text="Screenshot that shows the 'Metrics' page with the categories highlighted." lightbox="./media/monitor-virtual-wan-reference/metrics-page.png":::
40
+
:::image type="content" source="./media/monitor-virtual-wan-reference/metrics-page.png" alt-text="Screenshot that shows the 'Metrics' page with the categories highlighted." lightbox="./media/monitor-virtual-wan-reference/metrics-page.png":::
47
41
48
-
To see metrics for the virtual hub router, you can select **Metrics** from the virtual hub **Overview** page.
42
+
1.To see metrics for the virtual hub router, you can select **Metrics** from the virtual hub **Overview** page.
49
43
50
-
:::image type="content" source="./media/monitor-virtual-wan-reference/hub-metrics.png" alt-text="Screenshot that shows the virtual hub page with the metrics button." lightbox="./media/monitor-virtual-wan-reference/hub-metrics.png":::
44
+
:::image type="content" source="./media/monitor-virtual-wan-reference/hub-metrics.png" alt-text="Screenshot that shows the virtual hub page with the metrics button." lightbox="./media/monitor-virtual-wan-reference/hub-metrics.png":::
51
45
52
46
For more information, see [Analyze metrics for an Azure resource](../azure-monitor/essentials/tutorial-metrics.md).
53
47
@@ -86,30 +80,6 @@ When you review any metrics through Log Analytics, the output contains the follo
86
80
|Average|real|Equal to (Minimum + Maximum)/2|
87
81
|Total|real|Sum of the two metric values from both MSEEs (the main value to focus on for the metric queried)|
88
82
89
-
90
-
91
-
### Log Analytics sample query
92
-
93
-
If you selected to send diagnostic data to a Log Analytics Workspace, then you can use SQL-like queries, such as the following example, to examine the data. For more information, see [Log Analytics Query Language](/services-hub/health/log-analytics-query-language).
94
-
95
-
The following example contains a query to obtain site-to-site route diagnostics.
96
-
97
-
`AzureDiagnostics | where Category == "RouteDiagnosticLog"`
98
-
99
-
Replace the following values, after the `==`, as needed based on the tables reported in the previous section of this article.
100
-
101
-
- GatewayDiagnosticLog
102
-
- IKEDiagnosticLog
103
-
- P2SDiagnosticLog
104
-
- TunnelDiagnosticLog
105
-
- RouteDiagnosticLog
106
-
107
-
In order to run the query, you have to open the Log Analytics resource you configured to receive the diagnostic logs, and then select **Logs** under the **General** tab on the left side of the pane:
108
-
109
-
:::image type="content" source="./media/monitor-virtual-wan-reference/log-analytics-query-samples.png" alt-text="Screenshot of Log Analytics Query samples." lightbox="./media/monitor-virtual-wan-reference/log-analytics-query-samples.png":::
110
-
111
-
For Azure Firewall, a [workbook](../firewall/firewall-workbook.md) is provided to make log analysis easier. Using its graphical interface, you can investigate the diagnostic data without manually writing any Log Analytics query.
112
-
113
83
### <aname="create-diagnostic"></a>Create diagnostic setting to view logs
114
84
115
85
The following steps help you create, edit, and view diagnostic settings:
@@ -154,8 +124,6 @@ You can monitor the Secured Hub using Azure Firewall logs and metrics. You can a
@@ -164,8 +132,6 @@ You can monitor the Secured Hub using Azure Firewall logs and metrics. You can a
164
132
165
133
You can set alerts for any metric, log entry, or activity log entry listed in the [Azure Virtual WAN monitoring data reference](monitor-virtual-wan-reference.md).
This article provides configuration best practices for monitoring Virtual WAN and the different components that can be deployed with it. The recommendations presented in this article are mostly based on existing Azure Monitor metrics and logs generated by Azure Virtual WAN. For a list of metrics and logs collected for Virtual WAN, see the [Monitoring Virtual WAN data reference](monitor-virtual-wan-reference.md).
@@ -174,7 +140,7 @@ Most of the recommendations in this article suggest creating Azure Monitor alert
174
140
175
141
### Virtual WAN gateways
176
142
177
-
This section describes best practices for WAN gateways.
143
+
This section describes best practices for Virtual WAN gateways.
0 commit comments