Skip to content

Commit f5c160d

Browse files
committed
Migrate from MMA to AMA
1 parent bbe28bb commit f5c160d

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: Migrate to Azure Monitor Agent from Log Analytics agent
3+
description: Guidance for migrating to Azure Monitor Agent from MMA
4+
author: v-sreedevank
5+
ms.author: prijaisw
6+
ms.topic: conceptual
7+
ms.date: 08/07/2024
8+
9+
# Customer intent: As an azure administrator, I want to understand the process of migrating from the MMA agent to the AMA agent.
10+
11+
---
12+
13+
# Migrate to Azure Monitor Agent from Log Analytics agent
14+
15+
[Azure Monitor Agent (AMA)](./agents-overview.md) replaces the Log Analytics agent, also known as Microsoft Monitor Agent (MMA) and OMS, for Windows and Linux machines, in Azure and non-Azure environments, on-premises and other clouds. This article describes the impact on agent-based dependency analysis in lieu of Azure Monitor Agent (AMA) replacing the Log Analytics agent (also known as Microsoft Monitor agent (MMA)) and provides guidance to migrate from the Log Analytics agent to Azure Monitor Agent.
16+
17+
> [!IMPORTANT]
18+
> The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
19+
> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time. Ingestion for MMA will be unchanged until February 1 2025.
20+
> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
21+
> - **Customer Support:** You will not be able to get support for legacy agent issues.
22+
> - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
23+
24+
> [!Note]
25+
> Starting July 1, 2024, [standard Log Analytics charges](https://go.microsoft.com/fwlink/?linkid=2278207) are applicable for Agent-based dependency visualization. We suggest moving to [agentless dependency analysis](how-to-create-group-machine-dependencies-agentless.md) for a seamless experience.
26+
27+
## Migrate from MMA to AMA
28+
29+
1: To deploy the AMA agent, it is recommended to first clean up the existing Service Map to avoid duplicates. [Learn more](/azure/azure-monitor/vm/vminsights-migrate-from-service-map#remove-the-service-map-solution-from-the-workspace).
30+
31+
2: Review the [prerequisites](/azure/azure-monitor/agents/azure-monitor-agent-manage#prerequisites) for installing Azure Monitor Agent.
32+
33+
3: Download and run the script on the host machine.https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal#installation-options To get the AMA and the Dependency Agent deployed on the guest machine, the customer needs to create the Data collection rule (DCR) that maps to Log analytics workspace Id Collect data with Azure Monitor Agent - Azure Monitor | Microsoft Learn
34+
35+
In the transition scenario, the Log analytics workspace would be the same as the one that was configured for Service Map agent. DCR will allow the Customer to enable the collection of Processes and Dependencies. By default, it is disabled.
36+
37+
Log Analytics Size to estimate the price change customer will incur
38+
39+
The customer would be billed against the data volume per workspace. To know the volume of their workspace pls ask the customers to follow below steps
40+
41+
Customer logs in to the log analytics workspace.
42+
43+
Navigates to Logs section and run below query.
44+
45+
let AzureMigrateDataTables = dynamic(["ServiceMapProcess_CL","ServiceMapComputer_CL","VMBoundPort","VMConnection","VMComputer","VMProcess","InsightsMetrics"]); Usage | where StartTime >= startofday(ago(30d)) and StartTime < startofday(now()) | where DataType in (AzureMigrateDataTables) | summarize AzureMigateGBperMonth=sum(Quantity)/1000
46+
47+
Azure Migrate support for AMA(Greenfield customers)
48+
49+
Currently customer can download MMA agent via azure migrate portal. We will soon start supporting download of AMA agent via azure migrate portal.

0 commit comments

Comments
 (0)