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
title: How to view app dependencies with Azure Monitor for VMs (preview) | Microsoft Docs
3
-
description: Map is a feature of the Azure Monitor for VMs that automatically discovers application components on Windows and Linux systems and maps the communication between services. This article provides details on how to use it in a variety of scenarios.
3
+
description: Map is a feature of Azure Monitor for VMs. It automatically discovers application components on Windows and Linux systems and maps the communication between services. This article provides details on how to use the Map feature in various scenarios.
4
4
services: azure-monitor
5
5
documentationcenter: ''
6
6
author: mgoedtel
@@ -15,110 +15,124 @@ ms.date: 05/09/2019
15
15
ms.author: magoedte
16
16
---
17
17
18
-
# Using Azure Monitor for VMs (preview) Map to understand application components
19
-
Viewing the discovered application components on Windows and Linux virtual machines running in Azure your environmentcan be observed in two ways with Azure Monitor for VMs, from a virtual machine directly, or across groups of VMs from Azure Monitor.
18
+
# Use the Map feature of Azure Monitor for VMs (preview) to understand application components
19
+
In Azure Monitor for VMs, you can view discovered application components on Windows and Linux virtual machines (VMs) that run in Azure or your environment. You can observe the VMs in two ways. View a map directly from a VM or view a map from Azure Monitor to see the components across groups of VMs. This article will help you understand these two viewing methods and how to use the Map feature.
20
20
21
-
This article will help you understand the experience between the two perspectives and how to use the Map feature. For information about configuring Azure Monitor for VMs, see [Enable Azure Monitor for VMs](vminsights-enable-overview.md).
21
+
For information about configuring Azure Monitor for VMs, see [Enable Azure Monitor for VMs](vminsights-enable-overview.md).
22
22
23
23
## Sign in to Azure
24
-
Sign in to the Azure portal at [https://portal.azure.com](https://portal.azure.com).
24
+
Sign in to the [Azure portal](https://portal.azure.com).
25
25
26
-
## Introduction to Map experience
27
-
Before diving into viewing Map for a single virtual machine or group of VMs, it's important we provide a brief introduction to the feature so you understand how the information is presented and what the visualizations represent.
26
+
## Introduction to the Map experience
27
+
Before diving into the Map experience, you should understand how it presents and visualizes information. Whether you select the Map feature directly from a VM or from Azure Monitor, the Map feature presents a consistent experience. The only difference is that from Azure Monitor, one map shows all the members of a multiple-tier application or cluster.
28
28
29
-
Whether you select the Map feature directly from a VM or from Azure Monitor, it presents a consistent experience. The only difference is from Azure Monitor you can see all the members of a multi-tier application or cluster in one map.
29
+
The Map feature visualizes the VM dependencies by discovering running processes that have:
30
30
31
-
Maps visualizes the VMs dependencies by discovering running processes with active network connections between servers, inbound and outbound connection latency, and ports across any TCP-connected architecture over a specified time range. Expanding a VM shows process details and only those processes that communicate with the VM are shown. The count of front-end clients that connect into the virtual machine is indicated with the Client Group. The count of back-end servers the VM connects to are indicated on the Server Port Groups. Expand a Server Port Group to see the detailed list of servers connected over that port.
31
+
- Active network connections between servers.
32
+
- Inbound and outbound connection latency.
33
+
- Ports across any TCP-connected architecture over a specified time range.
34
+
35
+
Expand a VM to show process details and only those processes that communicate with the VM. The client group shows the count of front-end clients that connect into the VM. The server-port groups show the count of back-end servers the VM connects to. Expand a server-port group to see the detailed list of servers that connect over that port.
32
36
33
-
When you click on the virtual machine, the **Properties** pane is expanded on the right to show the properties of the item selected, such as system information reported by the operating system, properties of the Azure VM, and a doughnut summarizing the discovered connections.
37
+
When you select the VM, the **Properties** pane on the right shows the VM's properties. Properties include system information reported by the operating system, properties of the Azure VM, and a doughnut chart that summarizes the discovered connections.
34
38
35
-
On the right-side of the pane, click on the **Log Events**icon to switch focus of the pane to show a list of tables that collected data from the VM has sent to Azure Monitor and is available for querying. Clicking on any one of the record types listed will open the **Logs** page to view the results for that type with a pre-configured query filtered against the specific virtual machine.
41
+
On the rightside of the pane, select **Log Events** to show a list of data that the VM has sent to Azure Monitor. This data is available for querying. Select any record type to open the **Logs** page, where you see the results for that record type. You also see a preconfigured query that's filtered against the VM.
38
42
39
-
Close **Logs** and return to the **Properties** pane and select **Alerts** to view alerts that alerts raised for the VM from healthcriteria. Map integrates with Azure Alerts to show fired alerts for the selected server in the selected time range. The server displays an icon if there are current alerts, and the Machine Alerts pane lists the alerts.
45
+
Close the **Logs**page and return to the **Properties** pane. There, select **Alerts** to view VM health-criteria alerts. The Map feature integrates with Azure Alerts to show alerts for the selected server in the selected time range. The server displays an icon for current alerts, and the **Machine Alerts** pane lists the alerts.
42
46
43
-
To enable the Map feature to display relevant alerts, create an alert rule that fires for a specific computer. To create proper alerts:
46
-
- Include a clause to group by computer (for example, **by Computer interval 1 minute**).
47
-
- Choose to alert based on metric measurement.
49
+
To make the Map feature display relevant alerts, create an alert rule that applies to a specific computer:
48
50
49
-
For more information about Azure Alerts and creating alert rules, see [Unified Alerts in Azure Monitor](../../azure-monitor/platform/alerts-overview.md)
51
+
- Include a clause to group alerts by computer (for example, **by Computer interval 1 minute**).
52
+
- Base the alert on a metric.
50
53
51
-
The **Legend** option in the upper right-hand corner describes the symbols and roles on a map. To zoom in for a closer look at your map and move the it around, the Zoom controls at the bottom right-hand side of the page sets the zoom level and fit the page to the size of the current page.
54
+
For more information about Azure Alerts and creating alert rules, see [Unified alerts in Azure Monitor](../../azure-monitor/platform/alerts-overview.md).
55
+
56
+
In the upper-right corner, the **Legend** option describes the symbols and roles on the map. For a closer look at your map and to move it around, use the zoom controls in the lower-right corner. You can set the zoom level and fit the map to the size of the page.
52
57
53
58
## Connection metrics
54
-
The **Connections** pane displays standard connectivity metrics for the selected connection from the VM over the TCP port. The metrics include response time, requests per minute, traffic throughput, and links.
59
+
The **Connections** pane displays standard metrics for the selected connection from the VM over the TCP port. The metrics include response time, requests per minute, traffic throughput, and links.
57
62
58
63
### Failed connections
59
-
Failed connections are shown in the map for processes and computers, with a dashed red line indicating that a client system is failing to reach a process or port. Failed connections are reported from any system with the dependency agent if that system is the one attempting the failed connection. Map measures this process by observing TCP sockets that fail to establish a connection. This failure could result from a firewall, a misconfiguration in the client or server, or a remote service being unavailable.
64
+
The map shows failed connections for processes and computers. A dashed red line indicates a client system is failing to reach a process or port. For systems that use the Dependency agent, the agent reports on failed connection attempts. The Map feature monitors a process by observing TCP sockets that fail to establish a connection. This failure could result from a firewall, a misconfiguration in the client or server, or an unavailable remote service.
60
65
61
-
66
+
62
67
63
-
Understanding failed connections can help with troubleshooting, migration validation, security analysis, and understanding the overall architecture of the service. Failed connections are sometimes harmless, but they often point directly to a problem, such as a failover environment suddenly becoming unreachable, or two application tiers being unable to communicate with each other after a cloud migration.
68
+
Understanding failed connections can help you troubleshoot, validate migration, analyze security, and understand the overall architecture of the service. Failed connections are sometimes harmless, but they often point to a problem. Connections might fail, for example, when a failover environment suddenly becomes unreachable or when two application tiers can't communicate with each other after a cloud migration.
64
69
65
-
### Client Groups
66
-
Client Groups on the maprepresent client machines that have connections into the mapped machine. A single Client Group represents the clients for an individual process or machine.
70
+
### Client groups
71
+
On the map, client groups represent client machines that connect to the mapped machine. A single client group represents the clients for an individual process or machine.
67
72
68
-
73
+
69
74
70
-
To see the monitored clients and IP addresses of the systems in a Client Group, select the group. The contents of the group are listed beneath the group.
75
+
To see the monitored clients and IP addresses of the systems in a client group, select the group. The contents of the group appear below.
71
76
72
-
77
+
73
78
74
-
If the group includes monitored and un-monitored clients, you can select the appropriate section of the doughnut chart on the group to filter the clients.
79
+
If the group includes monitored and unmonitored clients, you can select the appropriate section of the group's doughnut chart to filter the clients.
75
80
76
-
### Server Port Groups
77
-
Server Port Groups represent server ports on servers that have inbound connections from the mapped machine. The group contains the server port and a count of the number of servers with connections to that port. Select the group to see the individual servers and connections listed.
81
+
### Server-port groups
82
+
Server-port groups represent ports on servers that have inbound connections from the mapped machine. The group contains the server port and a count of the number of servers that have connections to that port. Select the group to see the individual servers and connections.
78
83
79
-
84
+
80
85
81
-
If the group includes monitored and un-monitored servers, you can select the appropriate section of the doughnut chart on the group to filter the servers.
86
+
If the group includes monitored and unmonitored servers, you can select the appropriate section of the group's doughnut chart to filter the servers.
82
87
83
-
## View Map directly from a virtual machine
88
+
## View a map from a VM
84
89
85
-
To access Azure Monitor for VMs directly from a virtual machine, perform the following.
90
+
To access Azure Monitor for VMs directly from a VM:
86
91
87
92
1. In the Azure portal, select **Virtual Machines**.
88
-
2. From the list, choose a VM and in the **Monitoring** section choose **Insights (preview)**.
93
+
2. From the list, choose a VM. In the **Monitoring** section, choose **Insights (preview)**.
89
94
3. Select the **Map** tab.
90
95
91
-
Map visualizes the VMs dependencies, that is running process groups and processes with active network connections, over a specified time range. By default, the map shows the last 30 minutes. Using the **TimeRange** selector in the upper left-hand corner, you can query for historical time ranges of up to one hour to show how dependencies looked in the past (for example, during an incident or before a change occurred).
96
+
The map visualizes the VM's dependencies by discovering running process groups and processes that have active network connections over a specified time range.
97
+
98
+
By default, the map shows the last 30 minutes. If you want to see how dependencies looked in the past, you can query for historical time ranges of up to one hour. To run the query, use the **TimeRange** selector in the upper-left corner. You might run a query, for example, during an incident or to see the status before a change.
92
99
93
100
94
101
95
-
## View Map directly from a virtual machine scale set
102
+
## View a map from a virtual machine scale set
96
103
97
-
To access Azure Monitor for VMs directly from a virtual machine scale set, perform the following.
104
+
To access Azure Monitor for VMs directly from a virtual machine scale set:
98
105
99
106
1. In the Azure portal, select **Virtual machine scale sets**.
100
-
2. From the list, choose a VM and in the **Monitoring** section choose **Insights (preview)**.
107
+
2. From the list, choose a VM. Then in the **Monitoring** section, choose **Insights (preview)**.
101
108
3. Select the **Map** tab.
102
109
103
-
Map visualizes all of the instances in the scale set as a group node along with the group's dependencies. The expanded node lists the instances in the scale set, which you can scroll through ten at a time. To load a map for a specific instance, select that instance on the map, and then click on the ellipsis to it's right and choose **Load Server Map**. This will load the map for that instance, allowing you to see process groups and processes with active network connections over a specified time range. By default, the map shows the last 30 minutes. Using the **TimeRange** selector you can query for historical time ranges of up to one hour to show how dependencies looked in the past (for example, during an incident or before a change occurred).
110
+
The map visualizes all instances in the scale set as a group node along with the group's dependencies. The expanded node lists the instances in the scale set. You can scroll through these instances 10 at a time.
111
+
112
+
To load a map for a specific instance, first select that instance on the map. Then select the **ellipsis** button (...) to the right and choose **Load Server Map**. In the map that appears, you see process groups and processes that have active network connections over a specified time range.
113
+
114
+
By default, the map shows the last 30 minutes. If you want to see how dependencies looked in the past, you can query for historical time ranges of up to one hour. To run the query, use the **TimeRange** selector. You might run a query, for example, during an incident or to see the status before a change.
104
115
105
116
106
117
107
118
>[!NOTE]
108
-
>You can also access a map for a specific instance from the Instances view for your virtual machine scale set. Navigate to **Instances** under the **Settings** section, and then choose**Insights (preview)**.
119
+
>You can also access a map for a specific instance from the **Instances** view for your virtual machine scale set. In the **Settings** section, go to **Instances** >**Insights (preview)**.
109
120
110
-
## View Map from Azure Monitor
111
-
From Azure Monitor, the Map feature provides a global view of your virtual machines and their dependencies. To access the Map feature from Azure Monitor, perform the following.
121
+
## View a map from Azure Monitor
122
+
In Azure Monitor, the Map feature provides a global view of your VMs and their dependencies. To access the Map feature in Azure Monitor:
112
123
113
124
1. In the Azure portal, select **Monitor**.
114
-
2.Choose **Virtual Machines (preview)** in the **Insights** section.
125
+
2.In the **Insights** section, choose **Virtual Machines (preview)**.
129
+
130
+
Choose a workspace by using the **Workspace** selector at the top of the page. If you have more than one Log Analytics workspace, choose the workspace that's enabled with the solution and that has VMs reporting to it.
118
131
119
-
From the **Workspace** selector at the top of the page, if you have more than one Log Analytics workspace, choose the workspace that is enabled with the solution and has virtual machines reporting to it. The **Group** selector will return subscriptions, resource groups, [computer groups](../../azure-monitor/platform/computer-groups.md), and virtual machine scale sets of computers related to the selected workspace. Your selection only applies to the Map feature and does not carry over to Performance or Map.
132
+
The **Group** selector returns subscriptions, resource groups, [computer groups](../../azure-monitor/platform/computer-groups.md), and virtual machine scale sets of computers that are related to the selected workspace. Your selection applies only to the Map feature and doesn't carry over to Performance or Health.
120
133
121
-
By default, the map shows the last 30 minutes. Using the **TimeRange** selector, you can query for historical time ranges of up to one hour to show how dependencies looked in the past (for example, during an incident or before a change occurred).
134
+
By default, the map shows the last 30 minutes. If you want to see how dependencies looked in the past, you can query for historical time ranges of up to one hour. To run the query, use the **TimeRange** selector. You might run a query, for example, during an incident or to see the status before a change.
122
135
123
136
## Next steps
124
-
To learn how to use the health feature, see [View Azure VM Health](vminsights-health.md), or to identify bottlenecks and overall utilization with your VMs performance, see [View Azure Monitor for VMs Performance](vminsights-performance.md).
137
+
- To learn how to use the Health feature, see [View Azure VM health](vminsights-health.md).
138
+
- To identify bottlenecks, check performance, and understand overall utilization of your VMs, see [View performance status for Azure Monitor for VMs](vminsights-performance.md).
0 commit comments