{"id":169706,"date":"2007-01-06T11:11:47","date_gmt":"2007-01-06T11:11:47","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/project\/nethealth\/"},"modified":"2017-06-01T13:39:19","modified_gmt":"2017-06-01T20:39:19","slug":"nethealth","status":"publish","type":"msr-project","link":"https:\/\/www.microsoft.com\/en-us\/research\/project\/nethealth\/","title":{"rendered":"NetHealth"},"content":{"rendered":"

Overview<\/h2>\n

Networks are being deployed extensively in large corporations, small offices, and homes. However, a significant number of “pain points” remain for end-users and network administrators. To resolve complaints quickly and efficiently, network administrators need tools that can assist them in detecting, isolating, diagnosing, and correcting faults. Furthermore, such tools should also detect network security breaches, possibly caused by innocent employees. The NetHealth project<\/i> is about detecting, inferring, diagnosing, and recovering from user perceived performance problems in enterprise networks.<\/p>\n

Existing products do a reasonable job of presenting statistical data from the network. However, they do not do a comprehensive job of gathering and analyzing the data to establish the root cause of the problem. Furthermore, on the wireless side, most products gather data from the Access Points (APs) only and neglect the client-side view of the network. Some products that monitor the network from the client’s perspective require hardware sensors, which can be expensive to deploy and maintain. Also, current solutions do not provide any support for disconnected clients even though these are the ones that need the most help. On the wired side, a number of researchers have come up with solutions for diagnosing problems over WANs; however, most of those approaches are not integrated to perform end-to-end inference and diagnostics.<\/p>\n

Under the NetHealth umbrella, we are building algorithms and tools that<\/p>\n