Skip to content

Commit 621fab4

Browse files
Merge pull request #227390 from JeffreyWolford/patch-7
Update azure-monitor-agent-migration.md
2 parents ee99b45 + 9890fcf commit 621fab4

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/azure-monitor/agents/azure-monitor-agent-migration.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,10 @@ ms.custom: devx-track-azurepowershell, devx-track-azurecli
2121

2222
Azure Monitor Agent provides the following benefits over legacy agents:
2323

24-
- **Security and performance**
24+
- **Security**
2525
- Enhanced security through Managed Identity and Azure Active Directory (Azure AD) tokens (for clients).
26-
- Same events-per-second (EPS) upload rate with less resource utilization.
26+
- **Performance**
27+
- The AMA agent event throughput is 25% better than the MMA agent.
2728
- **Cost savings** by [using data collection rules](data-collection-rule-azure-monitor-agent.md). Using DCRs is one of the most useful advantages of using Azure Monitor Agent:
2829
- DCRs let you configure data collection for specific machines connected to a workspace as compared to the "all or nothing" approach of legacy agents.
2930
- With DCRs, you can define which data to ingest and which data to filter out to reduce workspace clutter and save on costs.
@@ -84,4 +85,4 @@ For more information, see:
8485

8586
- [Azure Monitor Agent overview](agents-overview.md)
8687
- [Azure Monitor Agent migration for Microsoft Sentinel](../../sentinel/ama-migrate.md)
87-
- [Frequently asked questions for Azure Monitor Agent migration](/azure/azure-monitor/faq#azure-monitor-agent)
88+
- [Frequently asked questions for Azure Monitor Agent migration](/azure/azure-monitor/faq#azure-monitor-agent)

0 commit comments

Comments
 (0)