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.
Powershell version 7.1.3or higher is recommended (minimum version 5.1)
Az Powershell moduleto pull workspace agent configuration information Az PowerShell module
- User will need Read/Write access to the specified workspace resource
- Connect-AzAccount and Select-AzSubscription will be used to set the context for the script to run so proper Azure credentials will be needed
To install DCR Config Generator:
Run the script using the sample parameters below:
.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -OutputFolder $outputFolderPath
Name Required Description
YES This is the subscription ID of the workspace
YES This is the resource Group of the workspace
YES This is the name of the workspace (Azure resource IDs are case insensitive)
YES The base name that will be used for each one the outputs DCRs
NO The output folder path. If not provided, the working directory path is used
For each supported
DCR type, the script produces a DCR ARM template (ready to be deployed) and a DCR payload (for users that don't need the ARM template). This is the list of currently supported DCR types:
- Windows contains
WindowsEventLogsdata sources only
- Linux contains
Syslogdata sources only
- Custom Logs contains
logFilesdata sources only:
- Each custom log gets its own DCR ARM template
- IIS Logs contains
iisLogsdata sources only
- Extensions contains
extensionsdata sources only along with any associated perfCounters data sources
VMInsights- If you would like to add support for a new extension type, please reach out to us.
- Windows contains
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.
New-AzResourceGroupDeployment -ResourceGroupName <resource-group-name> -TemplateFile <path-to-template>
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.