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
|**Virtual Hub Data Processed**| 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. |
27
+
This table contains more information about some of the metrics in the preceding table.
28
+
29
+
| Metric | Description |
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. |
30
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).
31
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%. |
32
34
@@ -38,6 +40,7 @@ The following table lists the metrics available for the microsoft.network/vpngat
These tables contain more information about some of the metrics in the preceding table.
41
44
42
45
#### Tunnel Packet Drop metrics
43
46
@@ -51,15 +54,15 @@ The following table lists the metrics available for the microsoft.network/vpngat
51
54
52
55
#### IPSec metrics
53
56
54
-
| Metric | Description|
55
-
|---|---|
57
+
| Metric | Description|
58
+
|:-------|:------------|
56
59
|**Tunnel MMSA Count**| Number of MMSAs getting created or deleted.|
57
60
|**Tunnel QMSA Count**| Number of IPSEC QMSAs getting created or deleted.|
58
61
59
62
#### Routing metrics
60
63
61
-
| Metric | Description|
62
-
|---|---|
64
+
| Metric | Description|
65
+
|:-------|:------------|
63
66
|**BGP Peer Status**| BGP connectivity status per peer and per instance.|
64
67
|**BGP Routes Advertised**| Number of routes advertised per peer and per instance.|
65
68
|**BGP Routes Learned**| Number of routes learned per peer and per instance.|
@@ -69,21 +72,19 @@ You can review per peer and instance metrics by selecting **Apply splitting** an
69
72
70
73
#### Traffic Flow metrics
71
74
72
-
| Metric | Description|
73
-
|---|---|
74
-
|**Gateway Bandwidth**| Average site-to-site aggregate bandwidth of a gateway in bytes per second.|
75
+
| Metric | Description|
76
+
|:-------|:------------|
77
+
|**Gateway S2S Bandwidth**| Average site-to-site aggregate bandwidth of a gateway in bytes per second.|
75
78
|**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.|
76
79
|**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.|
77
80
|**Tunnel Bandwidth**| Average bandwidth of a tunnel in bytes per second.|
78
81
|**Tunnel Egress Bytes**| Outgoing bytes of a tunnel. |
79
82
|**Tunnel Egress Packets**| Outgoing packet count of a tunnel. |
80
83
|**Tunnel Ingress Bytes**| Incoming bytes of a tunnel.|
81
-
|**Tunnel Ingress Packet**| Incoming packet count of a tunnel.|
84
+
|**Tunnel Ingress Packets**| Incoming packet count of a tunnel.|
82
85
|**Tunnel Peak PPS**| Number of packets per second per link connection in the last minute.|
83
86
|**Tunnel Flow Count**| Number of distinct 3-tuple (protocol, local IP address, remote IP address) flows created per link connection.|
84
87
85
-
86
-
87
88
### <aname="p2s-metrics"></a>Supported metrics for microsoft.network/p2svpngateways
88
89
89
90
The following table lists the metrics available for the microsoft.network/p2svpngateways resource type.
@@ -92,8 +93,8 @@ The following table lists the metrics available for the microsoft.network/p2svpn
|**Gateway P2S Bandwidth**| Average point-to-site aggregate bandwidth of a gateway in bytes per second. |
98
99
|**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**. |
99
100
| **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.
@@ -106,8 +107,8 @@ The following table lists the metrics available for the microsoft.network/expres
0 commit comments