Skip to content

Commit be05819

Browse files
committed
Warning fixes
1 parent f5c160d commit be05819

File tree

1 file changed

+23
-17
lines changed

1 file changed

+23
-17
lines changed
Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
22
title: Migrate to Azure Monitor Agent from Log Analytics agent
3-
description: Guidance for migrating to Azure Monitor Agent from MMA
3+
description: Procedure to migrate to Azure Monitor Agent from MMA
44
author: v-sreedevank
55
ms.author: prijaisw
6-
ms.topic: conceptual
6+
ms.topic: tutorial
77
ms.date: 08/07/2024
88

99
# Customer intent: As an azure administrator, I want to understand the process of migrating from the MMA agent to the AMA agent.
1010

1111
---
1212

13-
# Migrate to Azure Monitor Agent from Log Analytics agent
13+
# Migrate to Azure Monitor Agent
1414

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.
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.
1616

1717
> [!IMPORTANT]
1818
> 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.
@@ -22,28 +22,34 @@ ms.date: 08/07/2024
2222
> - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
2323
2424
> [!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.
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.
2626
27-
## Migrate from MMA to AMA
27+
## Migrate from Log analytics agent to Azure Monitor agent
2828

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).
29+
To migrate from Log analytics agent to Azure Monitor agent, follow these steps:
3030

31-
2: Review the [prerequisites](/azure/azure-monitor/agents/azure-monitor-agent-manage#prerequisites) for installing Azure Monitor Agent.
31+
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).
3232

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
33+
1. Review the [prerequisites](/azure/azure-monitor/agents/azure-monitor-agent-manage#prerequisites) to install the Azure Monitor Agent.
3434

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.
35+
1. Download and run the script on the host machine as detailed in [Installation options](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, create the [Data collection rule (DCR)](/azure/azure-monitor/agents/azure-monitor-agent-data-collection) that maps to the Log analytics workspace ID.
3636

37-
Log Analytics Size to estimate the price change customer will incur
37+
In the transition scenario, the Log analytics workspace would be the same as the one that was configured for Service Map agent. DCR allows you to enable the collection of Processes and Dependencies. By default, it is disabled.
3838

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
39+
### Estimate the price change
4040

41-
Customer logs in to the log analytics workspace.
42-
43-
Navigates to Logs section and run below query.
41+
You will be billed against the data volume per workspace. To know the volume of your workspace, follow these steps.
4442

43+
1. Sign in to the Log analytics workspace.
44+
1. Navigate to the **Logs** section and run the following query:
45+
46+
```
4547
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
48+
```
49+
50+
### Support for AMA in Azure Migrate
4651

47-
Azure Migrate support for AMA(Greenfield customers)
52+
Currently, you can download the MMA agent through the Azure Migrate portal. Support for downloading the AMA agent will be added shortly.
4853

49-
Currently customer can download MMA agent via azure migrate portal. We will soon start supporting download of AMA agent via azure migrate portal.
54+
## Next steps
55+
[Learn](how-to create-group-machine-dependencies.md) how to create dependencies for a group.

0 commit comments

Comments
 (0)