Skip to content

Commit 0d95a1c

Browse files
committed
Review comments
1 parent 4af7383 commit 0d95a1c

File tree

1 file changed

+16
-8
lines changed

1 file changed

+16
-8
lines changed

articles/migrate/azure-monitor-agent-migration.md

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,11 @@ ms.date: 08/07/2024
1010

1111
---
1212

13-
# Migrate to Azure Monitor Agent
13+
# Agent based dependency analysis using Azure monitor agent (AMA)
1414

15-
[Azure Monitor Agent (AMA)](/azure/azure-monitor/agents/azure-monitor-agent-overview) 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)](/azure/azure-monitor/agents/azure-monitor-agent-overview) 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.
16+
17+
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.
1618

1719
> [!IMPORTANT]
1820
> 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.
@@ -24,30 +26,36 @@ ms.date: 08/07/2024
2426
> [!Note]
2527
> 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.
2628
27-
## Migrate from Log analytics agent to Azure Monitor agent
29+
## Migrate from Log analytics agent (MMA) to Azure Monitor agent (AMA)
2830

2931
To migrate from Log analytics agent to Azure Monitor agent, follow these steps:
3032

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).
33+
1. To deploy the AMA agent, it's 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).
3234

3335
1. Review the [prerequisites](/azure/azure-monitor/agents/azure-monitor-agent-manage#prerequisites) to install the Azure Monitor Agent.
3436

3537
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.
3638

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.
39+
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's disabled.
3840

39-
### Estimate the price change
41+
## Estimate the price change
4042

4143
You will be billed against the data volume per workspace. To know the volume of your workspace, follow these steps.
4244

4345
1. Sign in to the Log analytics workspace.
4446
1. Navigate to the **Logs** section and run the following query:
4547

4648
```
47-
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
49+
let AzureMigrateDataTables = dynamic(["ServiceMapProcess_CL","ServiceMapComputer_CL","VMBoundPort","VMConnection","VMComputer","VMProcess","InsightsMetrics"]); Usage
50+
51+
| where StartTime >= startofday(ago(30d)) and StartTime < startofday(now())
52+
53+
| where DataType in (AzureMigrateDataTables)
54+
55+
| summarize AzureMigateGBperMonth=sum(Quantity)/1000
4856
```
4957
50-
### Support for AMA in Azure Migrate
58+
## Support for AMA in Azure Migrate
5159
5260
Currently, you can download the MMA agent through the Azure Migrate portal. Support for downloading the AMA agent will be added shortly.
5361

0 commit comments

Comments
 (0)