Azure Virtual WAN monitoring data reference
This article contains all the monitoring reference information for this service.
See Monitor Azure Virtual WAN for details on the data you can collect for Virtual WAN and how to use it.
Metrics
This section lists all the automatically collected platform metrics for this service. These metrics are also part of the global list of all platform metrics supported in Azure Monitor.
For information on metric retention, see Azure Monitor Metrics overview.
Supported metrics for Microsoft.Network/virtualhubs
The following table lists the metrics available for the Microsoft.Network/virtualhubs resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1Mindicates that the metric is sampled every minute,PT30Mevery 30 minutes,PT1Hevery hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
| Category | Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
|---|---|---|---|---|---|---|---|
| Scalability | Bgp Peer Status 1 - Connected, 0 - Not connected |
BgpPeerStatus |
Count | Maximum | routeserviceinstance, bgppeerip, bgppeertype |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Count Of Routes Advertised To Peer Total number of routes advertised to peer |
CountOfRoutesAdvertisedToPeer |
Count | Maximum | routeserviceinstance, bgppeerip, bgppeertype |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Count Of Routes Learned From Peer Total number of routes learned from peer |
CountOfRoutesLearnedFromPeer |
Count | Maximum | routeserviceinstance, bgppeerip, bgppeertype |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Routing Infrastructure Units Total number of routing infrastructure units, which represent the virtual hub's capacity |
RoutingInfrastructureUnits |
Count | Maximum | <none> | PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Spoke VM Utilization Number of deployed spoke VMs as a percentage of the total number of spoke VMs that the hub's routing infrastructure units can support |
SpokeVMUtilization |
Percent | Maximum | <none> | PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | 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: VNet to VNet (same hub and interhub) and branch to VNet (interhub). If a virtual hub is secured with routing intent, then these flows traverse the firewall instead of the hub router. |
VirtualHubDataProcessed |
Bytes | Total (Sum) | <none> | PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
This table contains more information about some of the metrics in the preceding table.
| Metric | Description |
|---|---|
| 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. |
| 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%. |
| Count Of Routes Advertised To Peer | The Virtual WAN hub router exchanges routes with all active instances of ExpressRoute gateways, VPN gateways and NVAs deployed in the Virtual WAN hub or in a connected Virtual Network spoke. When the Virtual WAN hub router learns a prefix with the same AS-PATH length from multiple peers, the router internally selects a peer to prefer for that specific route and re-advertises that route to all other peers (including the other gateway or NVA instance). This internal route selection process occurs for every route processed and the selected instance can change due to various factors such as network changes or maintenance events. As a result the number of routes advertised to an individual peer may fluctuate. When this metric is viewed with the maximum aggregation, Azure Monitor displays the data associated with a single BGP session between the Virtual WAN hub router and gateway or NVA. To effectively monitor changes or potential issues in your network, apply a split in Azure Monitor on the Count of Routes Advertised to Peer metric on a per peer IP address and ensure that the total number of routes advertised to your ExpressRoute, VPN or NVA is stable or in-line with any network changes. The total count of routes advertised must be calculated manually as the Azure Monitor sum aggregation type sums up data-points over the aggregation window, which does not accurately reflect routes advertised count. |
Supported metrics for microsoft.network/vpngateways
The following table lists the metrics available for the microsoft.network/vpngateways resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1Mindicates that the metric is sampled every minute,PT30Mevery 30 minutes,PT1Hevery hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
| Category | Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
|---|---|---|---|---|---|---|---|
| Traffic | Gateway S2S Bandwidth Site-to-site bandwidth of a gateway in bytes per second |
AverageBandwidth |
BytesPerSecond | Average | Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Routing | BGP Peer Status Status of BGP peer |
BgpPeerStatus |
Count | Average | BgpPeerAddress, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Routing | BGP Routes Advertised Count of Bgp Routes Advertised through tunnel |
BgpRoutesAdvertised |
Count | Total (Sum) | BgpPeerAddress, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Routing | BGP Routes Learned Count of Bgp Routes Learned through tunnel |
BgpRoutesLearned |
Count | Total (Sum) | BgpPeerAddress, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Gateway Inbound Flows Number of 5-tuple flows entering into a VPN gateway |
InboundFlowsCount |
Count | Maximum, Minimum | Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Ipsec | Tunnel MMSA Count MMSA Count |
MmsaCount |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Gateway Outbound Flows Number of 5-tuple flows exiting a VPN gateway |
OutboundFlowsCount |
Count | Maximum, Minimum | Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Ipsec | Tunnel QMSA Count QMSA Count |
QmsaCount |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Bandwidth Average bandwidth of a tunnel in bytes per second |
TunnelAverageBandwidth |
BytesPerSecond | Average | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Egress Bytes Outgoing bytes of a tunnel |
TunnelEgressBytes |
Bytes | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Errors | Tunnel Egress Packet Drop Count Count of outgoing packets dropped by tunnel |
TunnelEgressPacketDropCount |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Errors | Tunnel Egress TS Mismatch Packet Drop Outgoing packet drop count from traffic selector mismatch of a tunnel |
TunnelEgressPacketDropTSMismatch |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Egress Packets Outgoing packet count of a tunnel |
TunnelEgressPackets |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Ingress Bytes Incoming bytes of a tunnel |
TunnelIngressBytes |
Bytes | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Errors | Tunnel Ingress Packet Drop Count Count of incoming packets dropped by tunnel |
TunnelIngressPacketDropCount |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Errors | Tunnel Ingress TS Mismatch Packet Drop Incoming packet drop count from traffic selector mismatch of a tunnel |
TunnelIngressPacketDropTSMismatch |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Ingress Packets Incoming packet count of a tunnel |
TunnelIngressPackets |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel NAT Allocations Count of allocations for a NAT rule on a tunnel |
TunnelNatAllocations |
Count | Total (Sum) | NatRule, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel NATed Bytes Number of bytes that were NATed on a tunnel by a NAT rule |
TunnelNatedBytes |
Bytes | Total (Sum) | NatRule, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel NATed Packets Number of packets that were NATed on a tunnel by a NAT rule |
TunnelNatedPackets |
Count | Total (Sum) | NatRule, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel NAT Flows Number of NAT flows on a tunnel by flow type and NAT rule |
TunnelNatFlowCount |
Count | Total (Sum) | NatRule, FlowType, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Errors | Tunnel NAT Packet Drops Number of NATed packets on a tunnel that dropped by drop type and NAT rule |
TunnelNatPacketDrop |
Count | Total (Sum) | NatRule, DropType, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel Peak PPS Tunnel Peak Packets Per Second |
TunnelPeakPackets |
Count | Maximum | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | Tunnel Reverse NATed Bytes Number of bytes that were reverse NATed on a tunnel by a NAT rule |
TunnelReverseNatedBytes |
Bytes | Total (Sum) | NatRule, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel Reverse NATed Packets Number of packets on a tunnel that were reverse NATed by a NAT rule |
TunnelReverseNatedPackets |
Count | Total (Sum) | NatRule, ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Traffic | Tunnel Total Flow Count Total flow count on a tunnel |
TunnelTotalFlowCount |
Count | Total (Sum) | ConnectionName, RemoteIP, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Routing | VNet Address Prefix Count Count of Vnet address prefixes behind gateway |
VnetAddressPrefixCount |
Count | Total (Sum) | Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
These tables contain more information about some of the metrics in the preceding table.
Tunnel Packet Drop metrics
| Metric | Description |
|---|---|
| Tunnel Egress Packet Drop Count | Count of Outgoing packets dropped by tunnel. |
| Tunnel Ingress Packet Drop Count | Count of Incoming packets dropped by tunnel. |
| Tunnel NAT Packet Drops | Number of NATed packets dropped on a tunnel by drop type and NAT rule. |
| Tunnel Egress TS Mismatch Packet Drop | Outgoing packet drop count from traffic selector mismatch of a tunnel. |
| Tunnel Ingress TS Mismatch Packet Drop | Incoming packet drop count from traffic selector mismatch of a tunnel. |
IPSec metrics
| Metric | Description |
|---|---|
| Tunnel MMSA Count | Number of MMSAs getting created or deleted. |
| Tunnel QMSA Count | Number of IPSEC QMSAs getting created or deleted. |
Routing metrics
| Metric | Description |
|---|---|
| BGP Peer Status | BGP connectivity status per peer and per instance. |
| BGP Routes Advertised | Number of routes advertised per peer and per instance. |
| BGP Routes Learned | Number of routes learned per peer and per instance. |
| VNET Address Prefix Count | Number of virtual network address prefixes that the gateway uses and advertises. |
You can review per peer and instance metrics by selecting Apply splitting and choosing the preferred value.
Traffic Flow metrics
| Metric | Description |
|---|---|
| Gateway S2S Bandwidth | Average site-to-site aggregate bandwidth of a gateway in bytes per second. |
| Gateway Inbound Flows | Number of distinct 5-tuple flows (protocol, local IP address, remote IP address, local port, and remote port) flowing into a VPN Gateway. Limit is 250k flows. |
| Gateway Outbound Flows | Number of distinct 5-tuple flows (protocol, local IP address, remote IP address, local port, and remote port) flowing out of a VPN Gateway. Limit is 250k flows. |
| Tunnel Bandwidth | Average bandwidth of a tunnel in bytes per second. |
| Tunnel Egress Bytes | Outgoing bytes of a tunnel. |
| Tunnel Egress Packets | Outgoing packet count of a tunnel. |
| Tunnel Ingress Bytes | Incoming bytes of a tunnel. |
| Tunnel Ingress Packets | Incoming packet count of a tunnel. |
| Tunnel Peak PPS | Number of packets per second per link connection in the last minute. |
| Tunnel Total Flow Count | Number of distinct 3-tuple (protocol, local IP address, remote IP address) flows created per link connection. |
Supported metrics for microsoft.network/p2svpngateways
The following table lists the metrics available for the microsoft.network/p2svpngateways resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1Mindicates that the metric is sampled every minute,PT30Mevery 30 minutes,PT1Hevery hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
| Category | Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
|---|---|---|---|---|---|---|---|
| Traffic | Gateway P2S Bandwidth Point-to-site bandwidth of a gateway in bytes per second |
P2SBandwidth |
BytesPerSecond | Average | Instance |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Traffic | P2S Connection Count Point-to-site connection count of a gateway |
P2SConnectionCount |
Count | Total (Sum) | Protocol, Instance |
PT1M, PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Routing | User Vpn Route Count Count of P2S User Vpn routes learned by gateway |
UserVpnRouteCount |
Count | Total (Sum) | RouteType, Instance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
This table contains more information about some of the metrics in the preceding table.
| Metric | Description |
|---|---|
| Gateway P2S Bandwidth | Average point-to-site aggregate bandwidth of a gateway in bytes per second. |
| P2S Connection Count | Point-to-site connection count of a gateway. To ensure you're viewing accurate Metrics in Azure Monitor, select the Aggregation Type for P2S Connection Count as Sum. You can also select Max if you split By Instance. |
| User VPN Routes Count | Number of User VPN Routes configured on the VPN gateway. This metric can be broken down into Static and Dynamic Routes. |
Supported metrics for microsoft.network/expressroutegateways
The following table lists the metrics available for the microsoft.network/expressroutegateways resource type.
- All columns might not be present in every table.
- Some columns might be beyond the viewing area of the page. Select Expand table to view all available columns.
Table headings
- Category - The metrics group or classification.
- Metric - The metric display name as it appears in the Azure portal.
- Name in REST API - The metric name as referred to in the REST API.
- Unit - Unit of measure.
- Aggregation - The default aggregation type. Valid values: Average (Avg), Minimum (Min), Maximum (Max), Total (Sum), Count.
- Dimensions - Dimensions available for the metric.
- Time Grains - Intervals at which the metric is sampled. For example,
PT1Mindicates that the metric is sampled every minute,PT30Mevery 30 minutes,PT1Hevery hour, and so on. - DS Export- Whether the metric is exportable to Azure Monitor Logs via diagnostic settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
| Category | Metric | Name in REST API | Unit | Aggregation | Dimensions | Time Grains | DS Export |
|---|---|---|---|---|---|---|---|
| Traffic | Bits In Per Second Bits per second ingressing Azure via ExpressRoute Gateway which can be further split for specific connections |
ErGatewayConnectionBitsInPerSecond |
BitsPerSecond | Average | ConnectionName |
PT1M | No |
| Traffic | Bits Out Per Second Bits per second egressing Azure via ExpressRoute Gateway which can be further split for specific connections |
ErGatewayConnectionBitsOutPerSecond |
BitsPerSecond | Average | ConnectionName |
PT1M | No |
| Scalability | Active Flows Number of Active Flows on ExpressRoute Gateway |
ExpressRouteGatewayActiveFlows |
Count | Average, Minimum, Maximum | roleInstance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Performance | Bits Received Per second Total Bits received on ExpressRoute Gateway per second |
ExpressRouteGatewayBitsPerSecond |
BitsPerSecond | Average, Minimum, Maximum | roleInstance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Count Of Routes Advertised to Peer Count Of Routes Advertised To Peer by ExpressRoute Gateway |
ExpressRouteGatewayCountOfRoutesAdvertisedToPeer |
Count | Maximum | roleInstance, BgpPeerAddress |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Scalability | Count Of Routes Learned from Peer Count Of Routes Learned From Peer by ExpressRoute Gateway |
ExpressRouteGatewayCountOfRoutesLearnedFromPeer |
Count | Maximum | roleInstance, BgpPeerAddress |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Performance | CPU utilization CPU Utilization of the ExpressRoute Gateway |
ExpressRouteGatewayCpuUtilization |
Percent | Average, Minimum, Maximum | roleInstance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | Yes |
| Scalability | Frequency of Routes change Frequency of Routes change in ExpressRoute Gateway |
ExpressRouteGatewayFrequencyOfRoutesChanged |
Count | Total (Sum) | roleInstance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Max Flows Created Per Second Maximum Number of Flows Created Per Second on ExpressRoute Gateway |
ExpressRouteGatewayMaxFlowsCreationRate |
CountPerSecond | Maximum | roleInstance, direction |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Scalability | Number of VMs in the Virtual Network Number of VMs in the Virtual Network |
ExpressRouteGatewayNumberOfVmInVnet |
Count | Maximum | <none> | PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
| Performance | Packets received per second Total Packets received on ExpressRoute Gateway per second |
ExpressRouteGatewayPacketsPerSecond |
CountPerSecond | Average, Minimum, Maximum | roleInstance |
PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D | No |
This table contains more information about some of the metrics in the preceding table.
| Metric | Description |
|---|---|
| BitsInPerSecond | Bits per second ingressing Azure via ExpressRoute that can be further split for specific connections. |
| BitsOutPerSecond | Bits per second egressing Azure via ExpressRoute that can be further split for specific connections. |
| Bits Received Per Second | Total Bits received on ExpressRoute gateway per second. |
| CPU Utilization | CPU Utilization of the ExpressRoute gateway. |
| Packets received per second | Total Packets received on ExpressRoute gateway per second. |
| Count of routes advertised to peer | Count of Routes Advertised to Peer by ExpressRoute gateway. |
| Count of routes learned from peer | Count of Routes Learned from Peer by ExpressRoute gateway. |
| Frequency of routes change | Frequency of Route changes in ExpressRoute gateway. |
ExpressRoute gateway diagnostics
In Azure Virtual WAN, ExpressRoute gateway metrics can be exported as logs by using a diagnostic setting.
Metric dimensions
For information about what metric dimensions are, see Multi-dimensional metrics.
This service has the following dimensions associated with its metrics.
Microsoft.Network/virtualhubs
- bgppeerip
- bgppeertype
- routeserviceinstance
microsoft.network/vpngateways
- BgpPeerAddress
- ConnectionName
- DropType
- FlowType
- Instance
- NatRule
- RemoteIP
microsoft.network/p2svpngateways
- Instance
- Protocol
- RouteType
microsoft.network/expressroutegateways
- BgpPeerAddress
- ConnectionName
- direction
- roleInstance
Resource logs
This section lists the types of resource logs you can collect for this service. The section pulls from the list of all resource logs category types supported in Azure Monitor.
Supported resource logs for microsoft.network/p2svpngateways
| Category | Category display name | Log table | Supports basic log plan | Supports ingestion-time transformation | Example queries | Costs to export |
|---|---|---|---|---|---|---|
GatewayDiagnosticLog |
Gateway Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
IKEDiagnosticLog |
IKE Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
P2SDiagnosticLog |
P2S Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
This table contains more information about the preceding table.
| Metric | Description |
|---|---|
| Gateway Diagnostic Logs | Gateway-specific diagnostics such as health, configuration, service updates, and other diagnostics. |
| IKE Diagnostic Logs | IKE-specific diagnostics for IPsec connections. |
| 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. |
Supported resource logs for microsoft.network/vpngateways
| Category | Category display name | Log table | Supports basic log plan | Supports ingestion-time transformation | Example queries | Costs to export |
|---|---|---|---|---|---|---|
GatewayDiagnosticLog |
Gateway Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
IKEDiagnosticLog |
IKE Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
RouteDiagnosticLog |
Route Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
TunnelDiagnosticLog |
Tunnel Diagnostic Logs | AzureDiagnostics Logs from multiple Azure resources. |
No | No | Queries | No |
This table contains more information about the preceding table.
| Metric | Description |
|---|---|
| Gateway Diagnostic Logs | Gateway-specific diagnostics such as health, configuration, service updates, and other diagnostics. |
| 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. |
| Route Diagnostic Logs | Logs related to events for static routes, BGP, route updates, and other diagnostics. |
| IKE Diagnostic Logs | IKE-specific diagnostics for IPsec connections. |
Log Analytics sample query
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.
The following example contains a query to obtain site-to-site route diagnostics.
AzureDiagnostics | where Category == "RouteDiagnosticLog"
Replace the following values, after the ==, as needed based on the tables in this article.
- GatewayDiagnosticLog
- IKEDiagnosticLog
- P2SDiagnosticLog
- TunnelDiagnosticLog
- RouteDiagnosticLog
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:
For Azure Firewall, a workbook is provided to make log analysis easier. Using its graphical interface, you can investigate the diagnostic data without manually writing any Log Analytics query.
Azure Monitor Logs tables
This section lists the Azure Monitor Logs tables relevant to this service, which are available for query by Log Analytics using Kusto queries. The tables contain resource log data and possibly more depending on what is collected and routed to them.
Microsoft.Network/vpnGateways (Virtual WAN site-to-site VPN gateways)
Activity log
The linked table lists the operations that can be recorded in the activity log for this service. These operations are a subset of all the possible resource provider operations in the activity log.
For more information on the schema of activity log entries, see Activity Log schema.
Related content
- See Monitor Azure Virtual WAN for a description of monitoring Virtual WAN.
- See Monitor Azure resources with Azure Monitor for details on monitoring Azure resources.
- To learn how to monitor Azure Firewall logs and metrics, see Tutorial: Monitor Azure Firewall logs.