Supported metrics for Microsoft.Network/virtualHubs

The following table lists the metrics available for the Microsoft.Network/virtualHubs resource type.

Table headings

Metric - The metric display name as it appears in the Azure portal.
Name in Rest API - Metric name as referred to in the REST API.
Unit - Unit of measure.
Aggregation - The default aggregation type. Valid values: Average, Minimum, Maximum, Total, Count.
Dimensions - Dimensions available for the metric.
Time Grains - Intervals at which the metric is sampled. For example, PT1M indicates that the metric is sampled every minute, PT30M every 30 minutes, PT1H every 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.

For information on metric retention, see Azure Monitor Metrics overview.

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 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 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 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> PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D No
Traffic 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> 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> PT5M, PT15M, PT30M, PT1H, PT6H, PT12H, P1D No

Next steps