Hi @Handy, Frederick
Welcome to the Microsoft Q&A Platform. Thank you for posting your query here.
Please go through the below points:
- Azure Monitor for VM provides detailed performance metrics, including CPU utilization, memory, and network traffic at the VM level. Since your NVA is likely an Azure VM, enable VM Insights. For your reference: https://learn.microsoft.com/en-us/azure/azure-monitor/vm/tutorial-monitor-vm-enable-insights#:~:text=You%20can%20view,to%20your%20requirements.
- VM Insights can show you which processes running on your NVA VM are consuming the most CPU.
- This can help you confirm if the high CPU is related to network processing or another process. For your reference: https://learn.microsoft.com/en-us/azure/azure-monitor/vm/vminsights-overview#:~:text=It%20also%20monitors%20the%20performance%20of%20your%20virtual%20machines%20and%20virtual%20machine%20scale%20sets%20by%20collecting%20data%20on%20their%20running%20processes%20and%20dependencies%20on%20other%20resources.
- While it won't explicitly show Azure-to-Azure internal IPs, VM Insights might reveal the top active network connections in terms of bytes sent/received.
- If you see a large amount of traffic associated with an Azure internal IP range, it's a strong indicator of heavy Azure-to-Azure communication.
- Combine VM Insights data with Network Watcher Flow Logs and perform more granular analysis in Log Analytics
- In your flow logs, look for destination IPs within your Azure VNet ranges. This won't pinpoint the exact source, but it'll confirm if the traffic is internal to Azure.
- Enable NSG flow logs (specifically version 2) on the NSGs associated with your Hub and Spoke VNets, particularly the ones connected to your NVA's subnets.
- Use Log Analytics to query the flow logs, focusing on traffic within your Azure IP ranges. This can give you a better idea of which subnets are generating the most internal traffic.
Kindly let us know if the above helps or you need further assistance on this issue.
Thanks,
Sai.