Get Started with On-Premises Virtual Appliance

Before you deploy Splunk AppDynamics On-Premises Virtual Appliance, review the following prerequisites and requirements for the components.

Prerequisites

Make sure the following prerequisites are met:

VMware vSphere
  • Physical server(s) to host virtual machines.
  • VMWare ESXi and vSphere version >= 8.0.1
  • DNS IP, Gateway IP, and three host IP addresses.
  • For the hybrid deployment, you must be using Controller >= 24.2.2.
Microsoft Azure
  • An Azure account to deploy virtual machines.
  • Controller is >=24.2.2 for the hybrid deployment.
KVM

  • KVM hypervisor to run Virtual Machines.

  • The NTP service is enabled to synchronize time across hypervisors.
    CODE 
    $ timedatectl status
               Local time: Thu 2024-10-03 22:36:06 UTC
           Universal time: Thu 2024-10-03 22:36:06 UTC
                 RTC time: Thu 2024-10-03 22:36:06
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
  • The KVM is enabled in the server.
    CODE 
    $ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
  • The bridged device is available. Make a note of the device name to specify in the config.cfg file in a later step.

For more information, see Installing Ubuntu Server Considerations in Readme.md.

VMware ESXi
  • Physical server(s) to host virtual machines.
  • VMWare ESXi >= 8.0.1
  • DNS IP, Gateway IP, and three host IP addresses.
  • For the hybrid deployment, you must be using Controller >= 24.7.0.
AWS
  • An AWS account to deploy virtual machines.
  • Controller is >=24.2.2 for the hybrid deployment.
ROSA
Ensure that you have the following:
Note: Familiarize with Virtual Appliance CLI commands. See Virtual Appliance CLI.

Sizing Requirements

Review the CPU, memory, storage, node count, and throughput requirements for each Virtual Appliance deployment profile.

The following table shows Virtual Appliance installation profiles for each virtual machine:

Standard Deployment

Demo

Table 1. Hardware Requirements
Specification Min Node Count Max Agents

16 vCPUs, 32 GB RAM, 200 GB OS Disk, and minimum of 100 GB SSD Data Disk

 1 50
Table 2. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute 10,000
EUM Beacons/Minute Browser 1,000
Mobile 1,000
Synthetic Sessions/Minute 1,000

Small

Table 3. Hardware Requirements
Specification Min Node Count Max Agents

16 vCPUs, 64 GB RAM, 200 GB OS Disk, and 500 GB SSD Data Disk

 3 1,500
Table 4. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

250,000

Includes an Anomaly Detection limit up to 25,000.
EUM Beacons/Minute Browser 8,000
Mobile 15,000
Synthetic Sessions/Minute 7,500
OpenTelemetry Spans/Minute 24,000

Medium

Table 5. Hardware Requirements
Specification Throughput and IOPS Min Node Count Max Agents

32 vCPUs, 128 GB RAM, 200 GB OS Disk, and 3 TB SSD Data Disk

 GP3 Storage: 14,000 IOPS or 1,000 MB/s 3 1,500
Table 6. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

600,000

Includes an Anomaly Detection limit up to 60,000.
EUM Beacons/Minute Browser 20,000
Mobile 40,000
Synthetic Sessions/Minute 15,000
OpenTelemetry Spans/Minute 48,000

Large

Table 7. Hardware Requirements
Specification Throughput and IOPS Min Node Count Max Agents

64 vCPUs, 256 GB RAM, 200 GB OS Disk, and 5 TB SSD Data Disk

 GP3 Storage: 18,000 IOPS or 1,500 MB/s 3
  • 10000 Java Agents
  • 1000 Machine Agents
  • 5 Cluster Agents
Table 8. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

1,850,000

Includes an Anomaly Detection limit up to 185,000.
EUM Beacons/Minute Browser 40,000
Mobile 80,000
Synthetic Sessions/Minute 30,000
OpenTelemetry Spans/Minute 96,000

Extra Large

Table 9. Hardware Requirements
Specification Min Node Count Max Agents

128 vCPUs, 512 GB RAM, 200 GB OS Disk, and 10 TB SSD Data Disk

 3 14,500
Table 10. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

2,600,000

Includes an Anomaly Detection limit up to 260,000.
EUM Beacons/Minute Browser 80,000
Mobile 160,000
Synthetic Sessions/Minute 60,000
OpenTelemetry Spans/Minute 128,000
Hybrid Deployment

Demo

Table 11. Hardware Requirements
Specification Min Node Count Max Agents

16 vCPUs, 32 GB RAM, 200 GB OS Disk, and minimum of 100 GB SSD Data Disk

 1 50
Table 12. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute 10,000
EUM Beacons/Minute Browser 1,000
Mobile 1,000
Synthetic Sessions/Minute 1,000

Small

Table 13. Hardware Requirements
Specification Min Node Count Max Agents

16 vCPUs, 32 GB RAM, 200 GB OS Disk, and 500 GB SSD Data Disk

The memory heap size is set to 2 GB of available RAM

 3 2,000
Table 14. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

1,000,000

Includes an Anomaly Detection limit up to 100,000.
EUM Beacons/Minute Browser 10,000
Mobile 20,000
Synthetic Sessions/Minute 7,500
OpenTelemetry Spans/Minute 24,000

Medium

Table 15. Hardware Requirements
Specification Throughput and IOPS Min Node Count Max Agents

32 vCPUs, 64 GB RAM, 200 GB OS Disk, and 1 TB SSD Data Disk.

 GP3 Storage: 14,000 IOPS or 1,000 MB/s 3 7,500
Table 16. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

2,000,000

Includes an Anomaly Detection limit up to 200,000.
EUM Beacons/Minute Browser 20,000
Mobile 40,000
Synthetic Sessions/Minute 15,000
OpenTelemetry Spans/Minute 48,000

Large

Table 17. Hardware Requirements
Specification Throughput and IOPS Min Node Count Max Agents

64 vCPUs, 256 GB RAM, 200 GB OS Disk, and 2 TB SSD Data Disk.

 GP3 Storage: 18,000 IOPS or 1,500 MB/s 3
  • 20,000 Java Agents
  • 2,000 Machine Agents
Table 18. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

4,000,000

Includes an Anomaly Detection limit up to 400,000.
EUM Beacons/Minute Browser 40,000
Mobile 80,000
Synthetic Sessions/Minute 30,000
OpenTelemetry Spans/Minute 96,000

Extra Large

Table 19. Hardware Requirements
Specification Min Node Count Max Agents

128 vCPUs, 512 GB RAM, 200 GB OS Disk, and 10 TB SSD Data Disk.

 3 40,000
Table 20. Metrics Ingestion Limit
Services Limit
Max Metrics/Minute

7,500,000

Includes an Anomaly Detection limit up to 750,000.
EUM Beacons/Minute Browser 80,000
Mobile 160,000
Synthetic Sessions/Minute 60,000
OpenTelemetry Spans/Minute 192,000
Note: We recommend that your hosts have the capacity to run three additional virtual machines.

Deploy Splunk AppDynamics On-Premises Virtual Appliance

Complete the following steps to deploy Virtual Appliance:

Standard Deployment
1

Download the required image from the Virtual Appliance tab in the Downloads portal.

Note: Virtual Appliance is packaged in the OVA, VHD, and AMI formats. Choose the required format depending on your hypervisor type.
2

Deploy Splunk AppDynamics On-Premises Virtual Appliance or you can Bring Your Own Kubernetes (BYOK)

Note: You can review and update the parameters in the helm file. For more information about the helm file parameters, see Customize the Helm File.
3

Install Splunk AppDynamics Services as containers in the Standard Deployment
Hybrid Deployment
1

Download the required image from the Virtual Appliance tab in the Downloads portal.

Note: Virtual Appliance is packaged in the OVA, VHD, and AMI formats. Choose the required format depending on your hypervisor type.
2

Deploy Splunk AppDynamics On-Premises Virtual Appliance or you can Bring Your Own Kubernetes (BYOK)

Note: You can review and update the parameters in the helm file. For more information about the helm file parameters, see Customize the Helm File.
3

Install Splunk AppDynamics Services in the Hybrid Deployment.