Azure Virtual Network Gateway
Collect Azure Virtual Network Gateway Metrics data
Configuration¶
Install Func¶
It is recommended to enable Guance Integration - Extension - Managed Func: All prerequisites are automatically installed. Please continue with the script installation.
If you deploy Func on your own, refer to Self-deployed Func
Installation Script¶
Note: Please prepare the required Azure application registration information in advance and assign the
Monitoring Reader
role to the application registration.
To synchronize monitoring data for Azure Virtual Network Gateway, we install the corresponding collection script: 「Integration (Azure-Virtual Network Gateway Collection)」(ID: guance_azure_virtual_network_gateway
)
After clicking 【Install】, enter the corresponding parameters:
Azure Tenant ID
: Tenant IDAzure Client ID
: Application Registration Client IDAzure Client Secret Value
: Client secret value, note it's not the IDSubscriptions
: Subscription ID, multiple subscriptions separated by,
Click 【Deploy Startup Script】, and the system will automatically create a Startup
script set and automatically configure the corresponding startup script.
After enabling, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】to immediately run once without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs.
Validation¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding tasks have the corresponding automatic trigger configurations, and you can also check the corresponding task records and logs for any abnormalities.
- In Guance, 「Infrastructure - Resource Catalog」check if asset information exists.
- In Guance, 「Metrics」check if there are corresponding monitoring data.
Metrics¶
Collect Azure Virtual Network Gateway metrics. You can collect more metrics via configuration Supported metrics for microsoft.network/virtualnetworkgateways
Metric Name | Description | Unit |
---|---|---|
average_bandwidth_average |
Gateway S2S bandwidth | Bytes/s |
bgp_peer_status_average |
BGP peer status | count |
bgp_routes_advertised_total |
Advertised BGP routes | count |
bgp_routes_learned_total |
Learned BGP routes | count |
express_route_gateway_active_flows_average |
Number of active flows | count |
express_route_gateway_bits_per_second_average |
Bits received per second | Bytes/s |
express_route_gateway_count_of_routes_advertised_to_peer_maximum |
Count of routes advertised to peer | count |
express_route_gateway_count_of_routes_learned_from_peer_maximum |
Count of routes learned from peer | count |
express_route_gateway_cpu_utilization_average |
CPU utilization | % |
express_route_gateway_frequency_of_routes_changed_total |
Route change frequency | % |
express_route_gateway_max_flows_creation_rate_maximum |
Maximum number of flows created per second | count |
express_route_gateway_number_of_vm_in_vnet_maximum |
Number of VMs in virtual network | count |
express_route_gateway_packets_per_second_average |
Packets received per second | count |
inbound_flows_count_maximum |
Gateway inbound flows | % |
outbound_flows_count_maximum |
Gateway outbound flows | % |
vnet_address_prefix_count_total |
VNet address prefix count | count |
mesa_count_total |
Tunnel MMSA count | count |
qmsa_count_total |
Tunnel QMSA count | count |
tunnel_average_bandwidth_average |
Tunnel bandwidth | Bytes/s |
tunnel_egress_bytes_total |
Tunnel egress bytes | Byte |
tunnel_ingress_bytes_total |
Tunnel ingress bytes | Byte |
tunnel_egress_packets_total |
Tunnel egress packets | count |
tunnel_ingress_packets_total |
Tunnel ingress packets | count |