Open ehaslett opened 1 month ago
Hello @ehaslett , thanks for your feedback. We have captured this on the backlog for future planning - no ETA as of yet - for the missing part. We already have alerts for the following resources (which are of the same resource type involved in Virtual Wan):
Thanks, Bruno.
Hello @ehaslett , thanks for your feedback. We have captured this on the backlog for future planning - no ETA as of yet - for the missing part. We already have alerts for the following resources (which are of the same resource type involved in Virtual Wan):
- Firewall
- ExpressRouteGateways
- VpnGateways
Thanks, Bruno.
There are some resources that, while the same in functionality, have a different resource type for VWAN, like expressRouteGateway (vs virtualNetworkGateway used in VNets for both ER and VPN).
Check for previous/existing GitHub issues
Description
Request AMBA guidance for monitoring virtual WAN components where available. Some of this might be appropriate under specific resources with a tag of being VWAN managed. Virtual hubs, managed Route Server, managed Azure Firewall, managed ER GW, managed VPN GW, managed NVAs. It is unclear if the following can align or feed into AMBA guidance: https://learn.microsoft.com/en-us/azure/virtual-wan/azure-monitor-insights#detailed
Additional references: https://azure.github.io/Azure-Proactive-Resiliency-Library-v2/azure-resources/Network/virtualHubs/ https://learn.microsoft.com/en-us/azure/virtual-wan/monitor-virtual-wan#virtual-hub