Skip to content

Commit 56462e2

Browse files
authored
Merge pull request #206392 from guywi-ms/Migrate-from-Azure-Monitor-service-map-to-VM-insights
Migrate from Azure Monitor service map to VM Insights
2 parents dae947d + 091035e commit 56462e2

File tree

3 files changed

+49
-0
lines changed

3 files changed

+49
-0
lines changed

articles/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1186,6 +1186,8 @@ items:
11861186
href: vm/vminsights-dependency-agent-maintenance.md
11871187
- name: Map dependencies
11881188
href: vm/vminsights-maps.md
1189+
- name: Migrate from service map
1190+
href: vm/vminsights-migrate-from-service-map.md
11891191
- name: Monitor performance
11901192
href: vm/vminsights-performance.md
11911193
- name: Monitor guest health (preview)

articles/azure-monitor/vm/service-map.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.reviewer: Xema Pathak
1313

1414
Service Map automatically discovers application components on Windows and Linux systems and maps the communication between services. With Service Map, you can view your servers in the way that you think of them: as interconnected systems that deliver critical services. Service Map shows connections between servers, processes, inbound and outbound connection latency, and ports across any TCP-connected architecture, with no configuration required other than the installation of an agent.
1515

16+
> [!IMPORTANT]
17+
> Service map will be retired on 30 September 2025. To monitor connections between servers, processes, inbound and outbound connection latency, and ports across any TCP-connected architecture, make sure to [migrate to Azure Monitor VM insights](../vm/vminsights-migrate-from-service-map.md) before this date.
18+
1619
This article describes the details of onboarding and using Service Map. The prerequisites of the solution are the following:
1720

1821
* A Log Analytics workspace in a [supported region](vminsights-configure-workspace.md#supported-regions).
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Migrate from Service Map to Azure Monitor VM insights
3+
description: Migrate from Service Map to Azure Monitor VM insights to monitor the performance and health of virtual machines and scale sets, including their running processes and dependencies on other resources.
4+
ms.topic: conceptual
5+
author: guywi-ms
6+
ms.author: guywild
7+
ms.date: 09/13/2022
8+
ms.reviewer: xpathak
9+
10+
---
11+
12+
# Migrate from Service Map to Azure Monitor VM insights
13+
14+
[Azure Monitor VM insights](../vm/vminsights-overview.md) monitors the performance and health of your virtual machines and virtual machine scale sets, including their running processes and dependencies on other resources. This article explains how to migrate from [Service Map](../vm/service-map.md) to Azure Monitor VM insights, which provides a map feature similar to Service Map, along with other benefits.
15+
16+
> [!NOTE]
17+
> Service Map will be retired on 30 September 2025. Be sure to migrate to VM insights before this date to continue monitoring the communication between services.
18+
19+
The map feature of VM insights visualizes virtual machine dependencies by discovering running processes that have active network connection between servers, inbound and outbound connection latency, or ports across any TCP-connected architecture over a specified time range. For more information about the benefits of the VM insights map feature over Service Map, see [How is VM insights Map feature different from Service Map?](/azure/azure-monitor/faq#how-is-vm-insights-map-feature-different-from-service-map-).
20+
21+
## Enable VM insights using Azure Monitor Agent
22+
23+
VM insights uses [Azure Monitor Agent](../agents/agents-overview.md), which replaces the Log Analytics agent used by Service map. For more information about how to enable VM insights for Azure virtual machines and on-premises machines, see [How to enable VM insights using Azure Monitor Agent for Azure virtual machines](../vm/vminsights-enable-overview.md#agents).
24+
25+
If you have on-premises machines, we recommend enabling [Azure Arc for servers](../../azure-arc/servers/overview.md) so that you enable the virtual machines for VM insights using processes similar to Azure virtual machines.
26+
27+
VM insights also collects per-machine performance counters, which provide visibility into the health of your virtual machines. Azure Monitor Log ingests these performance counters every minute, which slightly increases monitoring costs per machine. [Learn more about the pricing](../vm/vminsights-overview.md#pricing).
28+
29+
30+
## Remove the Service Map solution from the workspace
31+
32+
Once you migrate to VM insights, remove the Service Map solution from the workspace to avoid data duplication and incurring extra costs:
33+
34+
1. Sign in to the [Azure portal](https://portal.azure.com/).
35+
1. In the search bar, type *Log Analytics workspaces*. As you begin typing, the list filters suggestions based on your input.
36+
1. Select **Log Analytics workspaces**.
37+
1. From your list of Log Analytics workspaces, select the workspace you chose when you enabled Service Map.
38+
1. On the left, select **Solutions**.
39+
1. From the list of solutions, select **ServiceMap(workspace name)**.
40+
1. On the **Overview** page for the solution, select **Delete**.
41+
1. When prompted to confirm, select **Yes**.
42+
43+
> [!IMPORTANT]
44+
> You won't be able to onboard new subscriptions to service map after 31 August 2024. The Service Map UI won't be available after 30 September 2025.

0 commit comments

Comments
 (0)