Leveraging OMS Network performance monitor to detect network loss
So a new interesting feature came up in my workspace (Network performance monitor) which allows us to monitor network performance between different endpoints. You can read more about it here –> https://azure.microsoft.com/en-us/documentation/articles/log-analytics-network-performance-monitor/#installing-and-configuring-agents-for-the-solution
But in case we can install the OMS agent on two nodes and the OMs agent will then be used to monitor and probe between the two nodes, it then creates a baseline of the health and can also be used to create a network topology map.
NOTE: At this time, this feature is only available for Windows agents, and if you have the OMS agent installed you need to run this PowerShell script to setup iplister on port 8084 and configure some registry keys this feature uses –> https://gallery.technet.microsoft.com/OMS-Network-Performance-04a66634/file/156805/1/EnableRules.ps1
After the PowerShell script has run, it takes about 2 – 5 minutes before the network mapping appears in the OMS workspace
Read the entire article here, Leveraging OMS Network performance monitor to detect network loss
via Marius Sandbu.