{"id":2806,"date":"2018-05-01T00:00:00","date_gmt":"2018-05-01T07:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/monitor-microsoft-peering-in-expressroute-with-network-performance-monitor-public-preview"},"modified":"2023-07-28T09:33:43","modified_gmt":"2023-07-28T16:33:43","slug":"monitor-microsoft-peering-in-expressroute-with-network-performance-monitor-public-preview","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/monitor-microsoft-peering-in-expressroute-with-network-performance-monitor-public-preview\/","title":{"rendered":"Monitor Microsoft peering in ExpressRoute with Network Performance Monitor – public preview"},"content":{"rendered":"

We are excited to announce the public preview of Network Performance Monitor\u2019s (NPM) new capability to monitor Microsoft peering in ExpressRoute<\/a>. This complements NPM\u2019s generally available capability to monitor ExpressRoute\u2019s Azure Private peering<\/a>. Throughout this post, I will walk you through some of the important use cases of the capability.<\/p>\n

Get complete visibility into the ExpressRoute connection to the Microsoft services<\/h2>\n

It can become extremely difficult to identify the bottleneck when a performance degradation is experienced while accessing a Microsoft service over ExpressRoute. This is because an ExpressRoute connection comprises of various components. With this capability, you can now get the required end-to-end visibility through NPM\u2019s interactive topology<\/a> view. You can not only view all the constituent components \u2013 on-premises network, circuit provider edge, ExpressRoute circuit, Microsoft edge, but also the latency contributed by each hop to help you identify the troublesome segment.<\/p>\n

The following snippet illustrates a topology view where the on-premises computer on the left is connected to the Microsoft service (outlook.office365.com) on the right, over primary and secondary ExpressRoute Microsoft peering connections. The service provider router at the customer edge and the Microsoft router at the Azure edge are also depicted. The on-premises hops (depicted by dashed lines) are initially compressed. From this map, you can view the latency contributed by each segment and identify the troublesome hop. You can also choose to expand the map to view all the on-premises hops and understand the latency contributed by them.<\/p>\n

\"image\"<\/p>\n

Monitor connectivity to Microsoft online services, over ExpressRoute<\/h2>\n

You can now monitor the end-to-end connectivity between your on-premises resources (branch offices, datacenters, and office sites) and Microsoft online services (Office 365, Dynamics 365, and Azure PaaS services) connected through an ExpressRoute. NPM proactively sends you alert notifications whenever the loss and latency of the connection shoots over the set threshold. You can catch transient issues by observing the performance trend charts, and drill-down deep into historical issues by viewing the past state of the system through the network state recorder<\/a>.<\/p>\n

Understand bandwidth utilization<\/h2>\n

The capability lets you view the bandwidth utilization trends for your Microsoft peering for both the primary and secondary circuits, and as a result, helps you in capacity planning.
\n\u00a0<\/p>\n

\"image\"
\nYou can also setup alerts to notify when the bandwidth for the peering crosses the threshold.
\n\u00a0<\/p>\n

Diagnose connectivity issues<\/h2>\n

NPM helps you diagnose several circuit connectivity issues, such as when the circuit is down, traffic is not flowing through the circuit, one of the primary or secondary connections is down, performance degradation due to peak utilization, etc. Visit the Diagnostics section in the ExpressRoute monitoring documentation<\/a> for more details.<\/p>\n

Create custom queries and views<\/h2>\n

All data that is exposed graphically through NPM\u2019s UI are also available natively in Log Analytics search<\/a>. You can perform interactive analysis of data in the repository, correlate data from different sources, create custom alerts and views, and export the data to Excel, PowerBI, or a shareable link.<\/p>\n

Get started<\/h2>\n

To get started, see the detailed instructions on how to setup ExpressRoute Monitor in NPM<\/a> and learn more about the other capabilities in NPM<\/a>.<\/p>\n

Please send your feedback<\/h2>\n

There are a few different routes to give feedback:<\/p>\n