Retirement Announcement - Start using the Azure Monitor agent instead of the Log Analytics agent before 31 August 2024

The Azure Monitor Agent is not open source.

Thank you, so none of the other agents send those, right?

It looks like we have some installed elsewhere when using this query.

Heartbeat  
| summarize arg_max(TimeGenerated, *) by SourceComputerId  
| sort by Computer  
| render table  

We are trying to set up an agent to send metrics and other logs to Azure Monitor for our On Prem servers and the documentation isn't clear on which things will work for both Windows and Unix/Ubuntu servers. The one document I've found indicates that this component here that we're being asked to remove is the one it says to use.

https://video2.skills-academy.com/en-us/azure/azure-monitor/agents/agents-overview#windows-agents

We're not using Azure-Arc for managing our on prem servers and don't plan to, though perhaps I'm misunderstanding what that's for. "Diagnostics Extension (WAD) doesn't seem to mention on prem support. Log Analytics agent is the one being decommissioned here. And Dependency agent says it requires Log Analytics to work.

For some IIS instances we can use Azure Application Monitor, but it only sees to support IIS and obviously doesn't support unix.
https://video2.skills-academy.com/en-us/azure/azure-monitor/app/status-monitor-v2-overview

We can use Application Insights SDK for other Windows Services and Windows Web Services, but again, that's not useful for unix and requires code changes to make work. We'll eventually get there but getting metrics and logs into Azure was a first step.

We are using MMA agent on Windows 10/11 computers that are not virtual machine.
The Azure Monitor agent is only available as a virtual machine extension. On hybrid machines, i have read that we need to use Azure Arc to deploy the Azure Monitor agent but that software is not compatible with Windows 10/11.

What will be the replacement for us ?

We are using the MMA with Azure Automation Account Update Management and I cannot find any mention if Azure Monitoring Agent supports/or will support Update Management feature.

Do you have any information about support of the Update Management with Azure Automation Account feature by AMA?
If the feature of Update Management with Azure Automation Account is not in the roadmap, then what is the future supported scenario for this functionality when MMA is retired?

We also need to understand what is happening to the update management component provided within an automation account. We use this extensively and utilise the pre and post script options heavily for running updates across our estate withe the pre/post scripts taking care of graceful stops and starts to our services.

We have looked to the new update management preview but it does not allow the pre/post script options, What is the migration path for this use case as this is quite a large feature to drop when moving to the new agent offering

It would be great to know if this is on the road map?

We are evaluating Azure Monitor for a network that does not have direct internet access. Some of my co-workers believe that log analytics gateway will be retired when log analytics agent is retired. Can anyone provide clarification on this?

Are there any specific migration details for AKS?

I'm a bit confused, since the Terraform provider is still referring to "oms_agent" and there is no hint about an "Azure Monitor Agent".

https://registry.terraform.io/providers/hashicorp/azurerm/3.98.0/docs/resources/kubernetes_cluster

Hi,

What will happen to VM's that are currently using the MMA after 31 August 2024?
Will the MMA no longer work? I am unable to find this anywhere on the MS documentation.

I'm also unsure what action (if any) is needed for AKS clusters. I use Bicep to deploy AKS clusters and specify an "omsagent" add-on profile (https://video2.skills-academy.com/en-us/azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#managedclusterpropertiesaddonprofiles).

However, my clusters appear to be using Azure Monitor Agent already - in my Log Analytics Workspace under "Agents", it says they are connected by Azure Monitor Agent. Also, if I list the pods on my cluster, there are pods starting with "ama-logs". Is there any action required on my part?

I can see the Bicep reference has an Azure Monitor profile (https://video2.skills-academy.com/en-us/azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#managedclusterazuremonitorprofilecontainerinsights) - is this something we should use instead, or is the omsagent add-on profile still OK?