AMA vs MMA which one should we go ahead???

In case you haven’t heard there’s a new agent in town. Its called the https://docs.microsoft.com/azure/azure-monitor/agents/agents-overview#azure-monitor-agent, this agent is brand new, re-written from the ground up and is going to replace the Microsoft Monitoring Agent (MMA) currently used by Log Analytics. This post will serve as both informational and opinion about the new agent. The new AMA is Generally Available, which means it is supported by Microsoft. Does that mean you should migrate to it? This first thing we need to talk about before getting into migration is Data Collection Rules.

Data Collection Rules

DCRs for short, represent a wholesale change in how our agents do data collection. Where Performance and Event logs were Log Analytics workspace wide with MMA, https://www.gnitcm.net/ with the new Azure Monitor Agent. Have a single special Event Log on a specific server you want to collect? We can do that now without collecting it from any other servers. Want to collect Event Logs for all production Hyper-V hosts, we can do that with a DCR now. Want to only collect CPU performance metrics for 5 servers? Again relatively easy with a DCR. This will help save on some costs in your data collection, if done correctly. As you will no longer be collecting Performance Metrics and Event Logs workspace wide. You can of course do that if you want, as well. However, this does represent a change that you will have to spend some time investigating how to incorporate into your monitoring scenario.