On this page:
This page lists the Synthetic Server requirements, offers sizing guidance, and shows you how to modify the default settings.
To deploy the Synthetic Server, you need to install the following AppDynamics platforms:
|Controller||4.5.0 and higher|
|Events Service||4.5.0 and higher|
Certain Synthetic Server features—specifically, Synthetic Sessions Analytics, features of Application Analytics that extend the functionality of Synthetic Sessions—require access to the AppDynamics Events Service.
The following table lists the requirements for deploying Synthetic Private Agents and Synthetic Hosted Agents.
|Synthetic Private Agents||See Requirements for the Synthetic Private Agent.|
|Synthetic Hosted Agents|
These requirements assume that the Synthetic Server is installed on a separate machine. If other AppDynamics platforms are installed on the same machine, the requirements (particularly for memory) could vary greatly and require many more resources.
NTP should be enabled on both the EUM Server host and the Controller machine. The machine clocks need to be able to synchronize.
You are required to have one EUM account for each on-premises deployment of the Synthetic Server. The machine hosting the Synthetic Server should be able to support 100 concurrent Synthetic Agents or 10 locations with 10 Synthetic Agents per location.
If you need the Synthetic Server to support more than 100 concurrent Synthetic Agents, see Increase the Synthetic Agent Support.
The Synthetic Server is supported on the following operating systems:
Linux (64 bit)
You can use the following file systems for machines that run Linux:
On-premises deployments on Linux are only supported on Intel architecture. Windows is not supported at this time.
The network settings on the operating system need to be tuned for high-performance data transfers. Incorrectly tuned network settings can manifest themselves as stability issues.
The following command listing demonstrates tuning suggestions for Linux operating systems. As shown, AppDynamics recommends a TCP/FIN timeout setting of 10 seconds (the default is typically 60), the TCP connection
keepalive time to 1800 seconds (reduced from 7200, typically), and disabling TCP window scale, TCP SACK, and TCP timestamps.
echo 5 > /proc/sys/net/ipv4/tcp_fin_timeout echo 1800 >/proc/sys/net/ipv4/tcp_keepalive_time echo 0 >/proc/sys/net/ipv4/tcp_window_scaling echo 0 >/proc/sys/net/ipv4/tcp_sack echo 0 >/proc/sys/net/ipv4/tcp_timestamps
The commands demonstrate how to configure the network settings in the
/proc system. To ensure the settings persist across system reboots, be sure to configure the equivalent settings in the
etc/sysctl.conf or the network stack configuration file appropriate for your operating system.
The Synthetic Server requires the following software to run and function correctly. You are required to have outbound internet access to install Python,
pip, and flake8.
The Synthetic Server requires JDK 8 to run services such as Synthetic Scheduler and Synthetic Shepherd.
You need to set the environmental variable
The Synthetic Server relies on Python to validate scripts.
If the machine where you're installing the Synthetic Server does not have Internet access, run the following steps to fetch and install
The Synthetic Server requires the
See How to Install libaio for instructions.
libaio on the host machine if it does not already have it installed. You may require outbound internet access if you don't have a locally hosted repository.
The following table provides instructions on how to install
libaio for some common flavors of the Linux operating system. Note, if you have a NUMA based architecture, then you are required to install the
|Red Hat and CentOS|
Install the library RPM from the Fedora website:
Use apt-get, such as:
|Debian||Use a package manager such as APT to install the library (as described for the Ubuntu instructions above).|