Tools for migrating from Log Analytics Agent to Azure Monitor Agent
Azure Monitor Agent (AMA) replaces the Log Analytics agent (also known as MMA and OMS) for Windows and Linux machines, in Azure and non-Azure environments, including on-premises and third-party clouds. The benefits of migrating to Azure Monitor Agent include enhanced security, cost-effectiveness, performance, manageability and reliability. This article explains how to use the AMA Migration Helper and DCR Config Generator tools to help automate and track the migration from Log Analytics Agent to Azure Monitor Agent.
Do not remove legacy agents being used by other Azure solutions or services. Use the migration helper to discover which solutions and services you use today.
The legacy Log Analytics agent will be deprecated by August 2024. After this date, Microsoft will no longer provide any support for the Log Analytics agent. Migrate to Azure Monitor agent before August 2024 to continue ingesting data.
Using AMA Migration Helper
AMA Migration Helper is a workbook-based Azure Monitor solution that helps you discover what to migrate and track progress as you move from Log Analytics Agent to Azure Monitor Agent. Use this single pane of glass view to expedite and track the status of your agent migration journey. The helper now supports multiple subscriptions, and includes automatic migration recommendations based on your usage.
You can access the workbook here, or find it on the Azure portal under Monitor > Workbooks > Public Templates > Azure Monitor essentials > AMA Migration Helper.
Automatic Migration Recommendations
Installing and using DCR Config Generator
Azure Monitor Agent relies only on data collection rules (DCRs) for configuration, whereas Log Analytics Agent inherits its configuration from Log Analytics workspaces.
Use the DCR Config Generator tool to parse Log Analytics Agent configuration from your workspaces and generate/deploy corresponding data collection rules automatically. You can then associate the rules to machines running the new agent using built-in association policies.
DCR Config Generator does not currently support additional configuration for Azure solutions or services dependent on Log Analytics Agent.
To install DCR Config Generator, you need:
- PowerShell version 5.1 or higher. We recommend using PowerShell version 7.1.3 or higher.
- Read access for the specified workspace resources.
Az Powershellmodule to pull workspace agent configuration information. Make sure
Az.OperationalInsightsmodules are installed.
- The Azure credentials for running
Select-AzContext, which set the context for the script to run.
To install DCR Config Generator:
Run the script:
Option 1: Outputs ready-to-deploy ARM template files only, which creates the generated DCR in the specified subscription and resource group, when deployed.
.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath
Option 2: Outputs ready-to-deploy ARM template files and the DCR JSON files separately for you to deploy via other means. You need to set the
.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath -GetDcrPayload
Parameter Required? Description
Yes ID of the subscription that contains the target workspace.
Yes Resource group that contains the target workspace.
Yes Name of the target workspace.
Yes Name of the new DCR.
Yes Region location for the new DCR.
No When set, it generates additional DCR JSON files
No Path in which to save the ARM template files and JSON files (optional). By default, Azure Monitor uses the current directory.
Review the output ARM template files. The script can produce two types of ARM template files, depending on the agent configuration in the target workspace:
- Windows ARM template and parameter files - if the target workspace contains Windows performance counters or Windows events.
- Linux ARM template and parameter files - if the target workspace contains Linux performance counters or Linux Syslog events.
If the Log Analytics workspace wasn't configured to collect data from connected agents, the generated files will be empty. This is a scenario in which the agent was connected to a Log Analytics workspace, but wasn't configured to send any data from the host machine.
Deploy the generated ARM templates:
In the portal's search box, type in template and then select Deploy a custom template.
Select Build your own template in the editor.
Paste the generated template into the editor and select Save.
On the Custom deployment screen, specify a Subscription, Resource group, and Region.
Select Review + create > Create.
You can include up to 100 'counterSpecifiers' in a data collection rule. 'samplingFrequencyInSeconds' must be between 1 and 300, inclusive.
Associate machines to your data collection rules:
- From the Monitor menu, select Data Collection Rules.
- From the Data Collection Rules screen, select your data collection rule.
- Select View resources > Add.
- Select your machines > Apply.
Submit and view feedback for