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
The following diagnostics are available for Virtual WAN point-to-site VPN gateways:
169
+
This table contains more information about the preceding table.
166
170
167
-
| Metric | Description|
168
-
|---|---|
171
+
| Metric | Description|
172
+
|:-------|:------------|
169
173
|**Gateway Diagnostic Logs**| Gateway-specific diagnostics such as health, configuration, service updates, and other diagnostics. |
170
174
|**IKE Diagnostic Logs**| IKE-specific diagnostics for IPsec connections.|
171
175
|**P2S Diagnostic Logs**| These events are User VPN P2S (Point-to-site) configuration and client events. They include client connect/disconnect, VPN client address allocation, and other diagnostics.|
@@ -174,15 +178,15 @@ The following diagnostics are available for Virtual WAN point-to-site VPN gatewa
|**Gateway Diagnostic Logs**| Gateway-specific diagnostics such as health, configuration, service updates, and other diagnostics.|
180
-
|**Tunnel Diagnostic Logs**| IPsec tunnel-related logs such as connect and disconnect events for a site-to-site IPsec tunnel, negotiated SAs, disconnect reasons, and other diagnostics. For connect and disconnect events, these logs also display the remote IP address of the corresponding on-premises VPN device.|
181
+
This table contains more information about the preceding table.
182
+
183
+
| Metric | Description |
184
+
|:-------|:------------|
185
+
|**Gateway Diagnostic Logs**| Gateway-specific diagnostics such as health, configuration, service updates, and other diagnostics. |
186
+
|**Tunnel Diagnostic Logs**| IPsec tunnel-related logs such as connect and disconnect events for a site-to-site IPsec tunnel, negotiated SAs, disconnect reasons, and other diagnostics. For connect and disconnect events, these logs also display the remote IP address of the corresponding on-premises VPN device. |
181
187
|**Route Diagnostic Logs**| Logs related to events for static routes, BGP, route updates, and other diagnostics. |
182
188
|**IKE Diagnostic Logs**| IKE-specific diagnostics for IPsec connections. |
Copy file name to clipboardExpand all lines: articles/virtual-wan/monitor-virtual-wan.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,15 +98,15 @@ The following example contains a query to obtain site-to-site route diagnostics.
98
98
99
99
`AzureDiagnostics | where Category == "RouteDiagnosticLog"`
100
100
101
-
Replace the following values, after the **= =**, as needed based on the tables reported in the previous section of this article.
101
+
Replace the following values, after the `==`, as needed based on the tables reported in the previous section of this article.
102
102
103
-
-"GatewayDiagnosticLog"
104
-
-"IKEDiagnosticLog"
105
-
-"P2SDiagnosticLog”
106
-
-"TunnelDiagnosticLog"
107
-
-"RouteDiagnosticLog"
103
+
- GatewayDiagnosticLog
104
+
- IKEDiagnosticLog
105
+
- P2SDiagnosticLog
106
+
- TunnelDiagnosticLog
107
+
- RouteDiagnosticLog
108
108
109
-
In order to execute 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:
109
+
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:
110
110
111
111
:::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":::
112
112
@@ -130,20 +130,21 @@ The following steps help you create, edit, and view diagnostic settings:
130
130
131
131
1. In this page, you can create a new diagnostic setting (**+Add diagnostic setting**) or edit an existing one (**Edit setting**). You can choose to send the diagnostic logs to Log Analytics (as shown in the following example), stream to an event hub, send to a 3rd-party solution, or archive to a storage account.
132
132
133
-
:::image type="content" source="./media/monitor-virtual-wan-reference/select-gateway-settings.png" alt-text="Screenshot for Select Diagnostic Log settings." lightbox="./media/monitor-virtual-wan-reference/select-gateway-settings.png":::
133
+
:::image type="content" source="./media/monitor-virtual-wan-reference/select-gateway-settings.png" alt-text="Screenshot for Select Diagnostic Log settings." lightbox="./media/monitor-virtual-wan-reference/select-gateway-settings.png":::
134
+
134
135
1. After clicking **Save**, you should start seeing logs appear in this log analytics workspace within a few hours.
135
136
1. To monitor a **secured hub (with Azure Firewall)**, then diagnostics and logging configuration must be done from accessing the **Diagnostic Setting** tab:
> Enabling these settings requires additional Azure services (storage account, event hub, or Log Analytics), which may increase your cost. To calculate an estimated cost, visit the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator).
If you chose to secure your virtual hub using Azure Firewall, relevant logs and metrics are available here: [Azure Firewall logs and metrics](../firewall/logs-and-metrics.md).
145
-
You can monitor the Secured Hub using Azure Firewall logs and metrics. You can also use activity logs to audit operations on Azure Firewall resources.
146
-
For every Azure Virtual WAN you secure and convert to a Secured Hub, Azure Firewall creates an explicit firewall resource object. The object is in the resource group where the hub is located.
146
+
147
+
You can monitor the Secured Hub using Azure Firewall logs and metrics. You can also use activity logs to audit operations on Azure Firewall resources. For every Azure Virtual WAN you secure and convert to a Secured Hub, Azure Firewall creates an explicit firewall resource object. The object is in the resource group where the hub is located.
147
148
148
149
:::image type="content" source="./media/monitor-virtual-wan-reference/firewall-resources-portal.png" alt-text="Screenshot shows a Firewall resource in the vWAN hub resource group." lightbox="./media/monitor-virtual-wan-reference/firewall-resources-portal.png":::
0 commit comments