Events Service Node Sizing Based on License Units
You can plan your hardware requirements with the data in the section. It describes recommended hardware configurations (in the context of Amazon EC2 instance types ) corresponding to the number of license entitlement units for Log and Transaction Analytics. See License Entitlements and Restrictions for details about license units for Log and Transaction Analytics.
For additional Events Service sizing information, see the following Splunk AppDynamics Community articles:
- Understanding EUM and Events Service concepts (describes the concepts necessary to build the profile)
- Build the Analytics traffic profile
- Size the Events Service and EUM using the profile (contains the Analytics Recipe Book for on-premises configuration)
- Limit EUM and Analytics usage (describes how to configure rules to enforce Analytics trade-offs when deploying Analytics on-premises)
The hardware shown for each license amount represents the hardware capacity of a theoretical combined load of both Transaction Analytics and Log Analytics events. The numbers used were derived from actual tests that were performed with an uncombined load, from which the following numbers were extrapolated. Note that the test conditions did not include query load and so may not be representative of a true production analytics environment.
Note that the retention can be 8, 30, 60 or 90 days which will directly affect storage requirements.
| Event Type | AWS Machine Instance Type | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| i2.2xlarge (61 GB RAM, 8 vCPU, 1600 GB SSD) | i2.4xlarge (122 GB RAM, 16 vCPU, 3200 GB SSD) | i2.8xlarge (244 GB RAM, 32 vCPU, 6400 GB SSD) | |||||||||
| 1 node | 3 nodes | 5 nodes | 7 nodes | 1 node | 3 nodes | 5 nodes | 7 nodes | 1 node | 3 nodes | 5 nodes | |
|
Transaction Analytics license units | 20 | 37 | 44 | 63 | 22 | 41 | 84 | 113 | 53 | 94 | 120 |
| Log Analytics license units | 7 | 10 | 17 | 19 | 16 | 19 | 32 | 44 | 39 | 116 | 270 |
The following points describe the test conditions under which the license units-to-hardware profile mappings in the table were generated:
- Average Log event size in bytes: 350
- Average size of business transaction event: 1 KB
- Tiers in business transaction: 3
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 the Events Service in a test environment that closely resembles your production application and user activity.