You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/network-watcher/connection-monitor-overview.md
+30-25Lines changed: 30 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: halkazwini
6
6
ms.author: halkazwini
7
7
ms.service: azure-network-watcher
8
8
ms.topic: concept-article
9
-
ms.date: 07/05/2024
9
+
ms.date: 12/13/2024
10
10
11
11
#CustomerIntent: As an Azure administrator, I need to monitor communication between one VM and another. If the communication fails, I need to know why so that I can resolve the problem.
Connection monitor provides unified, end-to-end connection monitoring in Network Watcher. The Connection monitor feature supports hybrid and Azure cloud deployments. Network Watcher provides tools to monitor, diagnose, and view connectivity-related metrics for your Azure deployments.
18
+
Connection monitor provides unified and continuous network connectivity monitoring, enabling users to detect anomalies, identify the specific network component responsible for issues, and troubleshoot with actionable insights in Azure and hybrid cloud environments.
19
19
20
-
Here are some use cases for Connection monitor:
20
+
Connection monitor tests measure aggregated packet loss and network latency metrics across TCP, ICMP, and HTTP pings. A unified topology visualizes the end-to-end network path, highlighting network path hops with hop performance metrics. Connection monitor provides actionable insights and detailed logs to efficiently analyze and troubleshoot the root cause of an issue.
21
21
22
-
- Your front-end web server virtual machine (VM) or virtual machine scale set communicates with a database server VM in a multi-tier application. You want to check network connectivity between the two VM/or scale sets.
23
-
- You want VMs/scale sets in, for example, the East US region to ping VMs/scale sets in the Central US region, and you want to compare cross-region network latencies.
24
-
- You have multiple on-premises office sites, one in Seattle, Washington, for example, and another in Ashburn, Virginia. Your office sites connect to Microsoft 365 URLs. For your users of Microsoft 365 URLs, you want to compare the latencies between Seattle and Ashburn.
25
-
- Your hybrid application needs connectivity to an Azure storage account endpoint. Your on-premises site and your Azure application connect to the same endpoint. You want to compare the latencies of the on-premises site with the latencies of the Azure application.
26
-
- You want to check the connectivity between your on-premises setups and the Azure VMs/virtual machine scale sets that host your cloud application.
27
-
- You want to check the connectivity from single or multiple instances of an Azure Virtual Machine Scale Set to your Azure or Non-Azure multi-tier application.
22
+
:::image type="content" source="./media/connection-monitor-overview/connection-monitor-diagram.png" alt-text="Diagram showing how Connection monitor interacts with Azure VMs, non-Azure hosts, endpoints, and data storage locations.":::
28
23
29
-
Here are some benefits of Connection monitor:
24
+
## Connection monitor use cases
30
25
31
-
* Unified, intuitive experience for Azure and hybrid monitoring needs
* Higher probing frequencies and better visibility into network performance
34
-
* Faster alerting for your hybrid deployments
35
-
* Support for connectivity checks that are based on HTTP, Transmission Control Protocol (TCP), and Internet Control Message Protocol (ICMP)
36
-
* Metrics and Log Analytics support for both Azure and non-Azure test setups
26
+
Here are some use cases of Connection monitor:
37
27
38
-
:::image type="content" source="./media/connection-monitor-2-preview/hero-graphic-new.png" alt-text="Diagram showing how Connection monitor interacts with Azure VMs, non-Azure hosts, endpoints, and data storage locations.":::
28
+
- Your front-end web server virtual machine (VM) communicates with a database server VM in a multi-tier application. You want to check network connectivity between the two VMs.
29
+
- You want to check the connectivity from single or multiple instances of an Azure Virtual Machine Scale Set to your Azure or non-Azure multi-tier application.
30
+
- You want to check the connectivity between your on-premises setups and the Azure VMs or scale sets that host your cloud application.
31
+
- You want VMs the East US region to ping VMs in the Central US region to measure and compare cross-region network latencies.
32
+
- You have on-premises office sites in Seattle, Washington, and Ashburn, Virginia, both connecting to Microsoft 365 URLs. You want to compare the latencies between these locations for your Microsoft 365 users.
33
+
- Your hybrid application requires connectivity to an Azure storage account endpoint, accessed by both your on-premises site and Azure application. You want to compare the latency of the on-premises site with that of the Azure application.
39
34
40
-
To start using Connection monitor for monitoring, follow these steps:
- Supported destination endpoints: Azure VMs, Azure virtual machine scale sets, Arc enabled on-premises hosts, URLs, FQDNs, and IP addresses. Destination endpoints don't require the Network Watcher extension.
44
+
45
+
- High probing frequencies and visibility into network performance
46
+
47
+
- End-to-end network path visibility with the Topology.
48
+
49
+
- Quick alerting for Azure and hybrid deployments.
50
+
51
+
- Support for connectivity checks that are based on HTTP, TCP, and ICMP.
52
+
53
+
- Metrics with Azure Monitor and logs with Azure Log Analytics.
49
54
50
55
## Install monitoring agents
51
56
@@ -244,7 +249,7 @@ On the dashboard, you can expand each connection monitor to view its test groups
244
249
245
250
You can filter a list based on:
246
251
247
-
***Top-level filters**: Search the list by text, entity type (Connection monitor, test group, or test) timestamp, and scope. Scope includes subscriptions, regions, sources, and destination types. See box 1 in the following image.
252
+
***Top-level filters**: Search the list by text, entity type (Connection monitor, test group, or test), timestamp, and scope. Scope includes subscriptions, regions, sources, and destination types. See box 1 in the following image.
248
253
***State-based filters**: Filter by the state of the connection monitor, test group, or test. See box 2 in the following image.
249
254
***Alert-based filter**: Filter by alerts that are fired on the connection monitor resource. See box 3 in the following image.
0 commit comments