Merge pull request #278801 from BrCutler/docs-editor/azure-monitor-agent-performanc-1718901197

Update azure-monitor-agent-performance.md

Author: prmerger-automator[bot]

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

@@ -11,18 +11,19 @@ ms.reviewer: jeffwo
 
 ---
 # Azure Monitor Agent Performance Benchmark
- 
-The agent can handle many thousands of events per second in the gateway event forwarding scenario. The exact throughput rate depends on various factors such as the size of each event, the specific data type, and physical hardware resources. This article will describe the Microsoft internal benchmark used for testing the agent throughput of 10k Syslog events in the forwarder scenario. The benchmark results should provide a guide to size the resources that you will need in your environment. 
- 
+
+The agent can handle many thousands of events per second in the gateway event forwarding scenario. The exact throughput rate depends on various factors such as the size of each event, the specific data type, and physical hardware resources. This article describes the Microsoft internal benchmark used for testing the agent throughput of 10k Syslog events in the forwarder scenario. The benchmark results should provide a guide to size the resources that you need in your environment.
+
 > [!NOTE]
 > The results in this article are informational about the performance of AMA in the forwarding scenario only and do not constitute any service agreement on the part of Microsoft.   
 
 ## Best practices for agent as a forwarder. 
 
+- Each AMA is limited to ingesting 20k EPS, and drops any data that exceeds the limits.
 - The forwarder should be on a dedicated system to eliminate potential interference from other workloads. 
 - The forwarder system should be monitored for CPU, memory, and disk utilization to prevent overloads from causing data loss. 
 - Where possible use a load balancer and redundant forwarder systems to improve reliability and scalability. 
-- For other considerations for forwarders see the Log Analytics Gateway documentation. 
+- For other considerations for forwarders, see the Log Analytics Gateway documentation. 
 
 ## Agent Performance 
 
@@ -39,7 +40,7 @@ The benchmarks are run on an Azure VM Standard_F8s_v2 system using AMA Linux ver
 - Max Disk IOPS:	6400 
 - Network:	12500 Mbp Max on all 4 physical NICs 
 
- 
+
 
 ## Results 
 
@@ -56,16 +57,16 @@ This section provides answers to common questions.
 
 ### How much data is sent per agent?
 
-The amount of data sent per agent depends on:
-          
+The amount of data sent per agent depends on:      
+
 * The solutions you've enabled.
 * The number of logs and performance counters being collected.
 * The volume of data in the logs.
-          
+
 See [Analyze usage in a Log Analytics workspace](../logs/analyze-usage.md).
-          
+
 For computers that are able to run the WireData agent, use the following query to see how much data is being sent:
-          
+
 ```kusto
 WireData
 | where ProcessName == "C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\MonitoringHost.exe"
@@ -74,12 +75,11 @@ WireData
 ```
 
 ### How much network bandwidth is used by the Microsoft Monitoring Agent when it sends data to Azure Monitor?
-        
+
 Bandwidth is a function of the amount of data sent. Data is compressed as it's sent over the network.
 
 ## Next steps
 
 - [Connect computers without internet access by using the Log Analytics gateway in Azure Monitor](gateway.md)
 - [Install the Azure Monitor Agent](azure-monitor-agent-manage.md) on Windows and Linux virtual machines.
 - [Create a data collection rule](data-collection-rule-azure-monitor-agent.md) to collect data from the agent and send it to Azure Monitor.
-