About a year ago, we launched the Azure Monitor Agent (or AMA) as a powerful new agent from Azure Monitor and a simpler world of data collection. A lot of you adopted it already. Some witnessed a 50% cost reduction with the agent's filtering capabilities while others saw a reduction of 2000 person-hours using Data Collection Rules to centrally manage agent configuration. We also made a bunch of improvements (view past releases) in response to your growing needs around security, reliability, supporting new information, resource types, distros, operating systems, and network perimeters, to make the agent even more powerful and resilient. If you haven't already, adopt and migrate to AMA today to get all the benefits with more coming soon!
Azure Monitor Agent was also created to consolidate legacy agents within Azure Monitor, especially the Log Analytics Agents (also referred to as "MMA" or "OMS" agent). With the Log Analytics agent retirement date of August 2024 getting closer, you should start testing and rolling out the new agent. Say goodbye to support ticket marathons, management headaches, unmanageable costs and security concerns by moving off of the legacy agents and adopting AMA today!
Here are some key benefits of migrating to AMA:
The short answer is - Start TODAY!
Besides serving as a means for you to collect data from your resources, other Azure services and solutions also use the agent as the to upload the data they require to Azure Monitor to then power their service/solution. If you've been waiting for Azure services and solutions to be available on AMA, your wait ends now. The following services are now in the general availability or public preview phase. which means you no longer need the legacy agent for these and can begin migrating to AMA:
Start testing and rolling out these features with AMA today, so that you're ready to deploy to production as soon as they hit general availability by end of this year. Testing earlier gives you the advantage of identifying potential blockers that may be specific to your organization's needs and that we'd love to eliminate for you sooner rather than later. Read our detailed migration guidance here.
There are numerous benefits to using AMA, but we understand that it could be a tedious process to migrate something as fundamental as the agent running on every machine. Downstream dependencies like dashboards and alerts must be validated as part of the migration to ensure there is no impact to business. We understand your pain and have created some tools to make the migration journey (depicted below) easier:
Note: For on premise servers or those managed by other clouds, you must first install the Arc agent (Connected Machine agent) if not already present. The Arc agent is the mechanism for non-Azure resources to install the agent extension and other virtual machine extensions available for Azure. Once you do this, at no added cost, you can simply follow the same guidance for migration (as depicted above) and overall agent management across Azure or non-Azure.
Here are the tools available today
...and we're not stopping here, there's more coming! As always, tell us what you need to make it simpler for you, and let us help you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.