Forum Discussion
Virtual WAN P2S Gateway Monitoring
We have recently setup Azure Virtual WAN and now have the P2S gateway running to see if this is a good solution for our remote access requirements. One thing I noticed is that if I look at the P2S ga...
Below may be the reasons why metrics not match:
- Portal vs Azure Monitor: The Azure portal shows real-time connected clients directly from the gateway resource, while Azure Monitor metrics may reflect aggregated or delayed data depending on the metric configuration and sampling interval.
- Metric Granularity: The metric P2SConnectedClients under Microsoft.Network/virtualHubs may not update instantly. It typically refreshes every 1–5 minutes, and may lag behind the live view.
- Data Source Differences: The portal view pulls from the gateway’s internal state, while Azure Monitor relies on telemetry emitted to the platform. These can diverge slightly in timing or completeness.
Suggest for Monitoring P2S Connections
- Use thAzure Workbook for P2S monitoring to visualize client connections, session durations, and trends.
- Set up Azure Monitor alerts on the P2SConnectedClients metric to track spikes or drops in usage.
- Consider enabling resource logs for deeper diagnostics, especially if you're troubleshooting connection issues or performance anomalies.