This page describes how to estimate the hardware requirements for a remote Analytics Agent deployment where a single Analytics Agent is aggregating transaction events from multiple APM Application Agents. This page describes transaction analytics only.
You should consider these two questions when sending analytics data to a remote Analytics Agent:
How many APM agents can report to one remote Analytics Agent?
What are the machine requirements for hosting the remote Analytics Agent?
Do not extract the numbers on this page to size for Log Analytics because you must install the Analytics Agent on the local machine to capture Log Analytics.
Analytics Agent Sizing Based on Event Volume
Based on our testing, the volume of events being sent to the Analytics Agent is the limiting factor in determining how many APM agents can report to one remote Analytics Agent.
The tests were conducted on virtual hardware and programmatically generated workload. Real-world workloads may vary. To best estimate your hardware sizing requirements, carefully consider the traffic patterns in your application and test in a test environment that closely resembles your production application and user activity.
Calculate Analytics Event Volume
One business transaction can traverse many tiers. In each tier, one business transaction traverses one node. One node produces one request per business transaction when the transaction is synchronous. For async transactions, multiple events may be generated by a node for a single request. One request equals one analytics event. To calculate how many events a business transaction generates, you need to count the number of tiers/nodes that are sending data into the Analytics Agent.
You can estimate the number of events using the following formula:
One business transaction generates events at a rate = calls per minute times the number of tiers reporting analytics data for the business transaction.
In simple terms: #events for one business transaction = calls per minute times # of tiers.