Migrate from Microsoft Monitoring Agent (MMA) to the Azure Monitoring Agent (AMA)
Microsoft is retiring the Microsoft Monitoring agent (MMA) in August 2024. It is recommended that all customers move to the new Azure Monitoring Agent (AMA) before this date to avoid disruption. Within Nerdio Manager, we allow customers to manage this transition by selecting the preferred monitoring approach.
New Nerdio Manager deployments as of v5.7 use the Azure Monitor Agent by default, so no changes are necessary.
The Azure Monitor Agent communicates with the selected Log Analytics Workspace (LAW) using data collection rules. The AMA has a separate extension that is installed on a VM and can be installed without removing the old Microsoft Monitoring Agent. Both extensions can operate at the same time.
Follow these steps if you wish to review your configuration or prevent the deployment of the AMA agent to your environment.
To review your configuration:
Navigate to Settings > Integrations.
In the Azure Monitor Insights, next to Current status, select Enabled.
Scroll down to the bottom to review the option Use Azure Monitor Agent (AMA).
Select Use Azure Monitor Agent (AMA) to have all new host pools use Azure Monitoring Agent. Alternatively, unselect this option to have all new host pools use the legacy Microsoft Monitoring Agent.
Note: This change does not apply by default to existing host pools.
Follow these steps if you wish if you wish to enable the Azure Monitoring Agent on existing host pools.
To enable AMA on existing host pools:
Locate the host pool you wish to work with.
From the action menu, select Properties > Azure Monitor.
Select Use Azure Monitor Agent (AMA).
Optionally, select Apply to existing hosts to deploy the agent to existing hosts.
Note: Deploying AMA to existing hosts should be avoided during working hours. Use the scheduler to deploy during non-working hours.