Merge pull request #263732 from siddomala/RHCvirtualhub

RHC for Virtual WAN

Author: prmerger-automator[bot]

articles/service-health/resource-health-checks-resource-types.md

@@ -195,6 +195,11 @@ Below is a complete list of all the checks executed through resource health by r
 |---|
 | - Is the ExpressRoute circuit healthy?|
 
+## Microsoft.Network/expressRouteGateways (ExpressRoute Gateways in Virtual WAN)
+|Executed Checks|
+|---|
+| - Is the ExpressRoute Gateway up and running?|
+
 ## Microsoft.network/frontdoors
 |Executed Checks|
 |---|
@@ -216,6 +221,11 @@ Below is a complete list of all the checks executed through resource health by r
 |---|
 | - Are there any issues impacting the Traffic Manager profile?|
 
+## Microsoft.Network/virtualHubs
+|Executed Checks|
+|---|
+| - Is the virtual hub router up and running?|
+
 ## Microsoft.network/virtualNetworkGateways
 |Executed Checks|
 |---|

articles/virtual-wan/monitoring-best-practices.md

@@ -122,6 +122,16 @@ This section of the article focuses on metric-based alerts. Azure Firewall offer
 |Create alert rule for risk of SNAT port exhaustion.|Azure Firewall provides 2,496 SNAT ports per public IP address configured per backend virtual machine scale instance. It’s important to estimate in advance the number of SNAT ports that will fulfill your organizational requirements for outbound traffic to the Internet. Not doing so increases the risk of exhausting the number of available SNAT ports on the Azure Firewall, potentially causing outbound connectivity failures.<br><br>Use the **SNAT port utilization** metric to monitor the percentage of outbound SNAT ports currently in use. Create an alert rule for this metric to be triggered whenever this percentage surpasses **95%** (due to an unforeseen traffic increase, for example) so you can act accordingly by configuring an additional public IP address on the Azure Firewall, or by using an [Azure NAT Gateway](../nat-gateway/nat-overview.md) instead. Use the **Maximum** aggregation type when configuring the alert rule.<br><br>To learn more about how to interpret the **SNAT port utilization** metric, see [Overview of Azure Firewall logs and metrics](../firewall/logs-and-metrics.md#metrics). To learn more about how to scale SNAT ports in Azure Firewall, see [Scale SNAT ports with Azure NAT Gateway](../firewall/integrate-with-nat-gateway.md).|
 |Create alert rule for firewall overutilization.|Azure Firewall maximum throughput differs depending on the SKU and features enabled. To learn more about Azure Firewall performance, see [Azure Firewall performance](../firewall/firewall-performance.md).<br><br>You might want to be alerted if your firewall is nearing its maximum throughput and troubleshoot the underlying cause, as this can have an impact in the firewall’s performance.<br><br> Create an alert rule to be triggered whenever the **Throughput** metric surpasses a value nearing the firewall’s maximum throughput – if the maximum throughput is 30Gbps, configure 25Gbps as the **Threshold** value, for example. The **Throughput** metric unit is **bits/sec**. Choose the **Average** aggregation type when creating the alert rule.
 
+## Resource Health Alerts
+
+You can also configure [Resource Health Alerts](../service-health/resource-health-alert-monitor-guide.md) via Service Health for the below resources. This ensures you are informed of the availability of your Virtual WAN environment, and this allows you to troubleshoot if networking issues are due to your Azure resources entering an unhealthy state, as opposed to issues from your on-premises environment. It is recommended to configure alerts when the resource status becomes degraded or unavailable. If the resource status does become degraded/unavailable, you can analyze if there are any recent spikes in the amount of traffic processed by these resources, the routes advertised to these resources, or the number of branch/VNet connections created. Please see [Azure Virtual WAN limits](../azure-resource-manager/management/azure-subscription-service-limits.md#virtual-wan-limits) for additional info on limits supported in Virtual WAN. 
+
+* Microsoft.Network/vpnGateways
+* Microsoft.Network/expressRouteGateways
+* Microsoft.Network/azureFirewalls
+* Microsoft.Network/virtualHubs
+* Microsoft.Network/p2sVpnGateways
+
 ## Next steps
 
 * See [Monitoring Virtual WAN data reference](monitor-virtual-wan-reference.md) for a data reference of the metrics, logs, and other important values created by Virtual WAN.

includes/virtual-wan-limits.md

@@ -19,3 +19,6 @@
 | VNet connections per hub  | 500 minus total number of hubs in Virtual WAN |
 | Aggregate throughput per Virtual WAN hub router | 50 Gbps for VNet to VNet transit |
 | VM workload across all VNets connected to a single Virtual WAN hub | 2000 (If you want to raise the limit or quota above the default limit, see [hub settings](../articles/virtual-wan/hub-settings.md)). |
+| Total number of routes the hub can accept from its connected resources (virtual networks, branches, other virtual hubs, etc.) | 10,000 |
+
+