Controller Sizing
The following table shows Controller installation profiles by metric ingestion rate and node count. As previously noted, the actual metrics generated by a node can vary greatly depending on the nature of the application on the node and the Splunk AppDynamics configuration. Be sure to validate your sizing against the metric ingestion rate before deploying to production.
| Profile | Max Metrics/Minute | Max Agents (Approx) | OS | Linux Compute | Windows Compute | Storage |
|---|---|---|---|---|---|---|
| Demo | 10,000 | 5 | Linux or Windows | 2 Cores, 8 GB RAM | 2 Cores, 8 GB RAM | 50 GBNote: This profile is not supported when installing with Aurora DB. |
| Small | 50,000 | 50 | Linux or Windows | 4 Cores, 16 GB RAM | 4 Cores, 16 GB RAM | 400 GBNote: This profile is not supported when installing with Aurora DB. |
| Medium | 1,000,000 | 2,000 | Linux or Windows | Bare-metal: 8 Cores, 128GB RAM | Bare-metal: 8 Cores, 128 GB RAM | 5 TB SAS SSDs. Hardware-based RAID 5 configuration |
| Linux or Windows | VM: 16 vCPUs, 128GB RAM | VM: 16 vCPUs, 128 GB RAM | 5 TB SSD-based SAN with 10 Gb/s FCoE | |||
| Large | 5,000,000 | 15,000 | Linux |
Bare-metal: 28 cores, 512 GB RAM VM: 32 vCPUs, 256GB RAM | N/A |
|
| Extra Large |
For deployments that exceed the Large profile configuration defined here, contact Splunk AppDynamics Professional Services for a thorough viability evaluation of your Controller. |
Amazon Web Services (AWS) Sizing for On-Premises
| AWS Profile with Aurora | Max Metrics/Minute | Max Agents (Approx) | OS | Compute | Instance Size for AWS Aurora Storage | Block Storage (for Controller application files only)* |
|---|---|---|---|---|---|---|
| Medium | 1,000,000 | 1500 | Linux | EC2: r4.2xlarge | db.r4.4xlarge | 10 GB GP2 EBS Volume. We recommend using a different volume than the instance's root volume. |
| Large | 5,000,000 | 10000 | Linux | EC2: r4.8xlarge | db.r4.16xlarge | 10 GB GP2 EBS Volume. We recommend using a different volume than the instance's root volume. |
* The specified disk space must be available for use by the Controller. Specifications do not include overhead from the operating system, file system, and so on.
Elastic Network Interface (ENI)
The ENI numbers were last updated on Feb 28, 2018.
For AWS, provision an ENI for each Controller host and link the license to the MAC address of the ENI. For more information about ENI, see AWS documentation.