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

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

Standard Deployment
Profile Specification Min Node Count Max Agents Max Metrics/Minute EUM Beacons/Minute Synthetic Sessions/Minute OpenTelemetry Spans/Minute
Browser Mobile
Demo

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

1

50

10000

1000

1000

1000

-
Small

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

3

1500

250,000

Includes an Anomaly Detection limit up to 25,000.

8000

15000

7500

24000

Medium

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

3

3500

600,000

Includes an Anomaly Detection limit up to 60,000.

20000

40000

15000

48000

Large

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

3

  • 10000 Java Agents
  • 1000 Machine Agents
  • 5 Cluster Agents

1,850,000

Includes an Anomaly Detection limit up to 185,000.

40000

80000

30000

96000

Extra Large

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

3

14,500

2,600,000

Includes an Anomaly Detection limit up to 260,000.

80000

160000

60000

1.28,000

Hybrid Deployment
Profile Specification Min Node Count Max Agents Max Metrics/Minute EUM Beacons/Minute Synthetic Sessions/Minute OpenTelemetry Spans/Minute
Browser Mobile
Demo

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

1

50

10000

1000

1000

1000

-

Small

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

3

2000

1,000,000

Includes an Anomaly Detection limit up to 100,000.

10000

20000

7500

24000

Medium

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

3

7500

2,000,000

Includes an Anomaly Detection limit up to 200,000.

20000

40000

15000

48000

Large

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

3
  • 20000 Java Agents
  • 2000 Machine Agents

4,000,000

Includes an Anomaly Detection limit up to 400,000.

40000

80000

30000

96000

Extra Large

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

3 40,000

7,500,000

Includes an Anomaly Detection limit up to 750,000.

80000

160000

60000

1,92,000

Note: We recommend that your hosts have the capacity to run additional three 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

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

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.