Synthetic Server Deployment Architecture

The following sections describe and provide diagrams of the different on-premises Synthetic Server deployments. The diagrams show the connections and data flow between the components of the deployments. For information about the other Splunk AppDynamics On-Premises platform components, see Platform Components and Platform Connections.

Synthetic Private Agents Deployment

The following diagram shows the connections and data flow between the on-premises Synthetic Server and the EUM Server and Synthetic Private Agents.

Synthetic Server Connections

The following table lists and describes the traffic flow between the Synthetic Server and the other components.

Connection Source Destination Protocol Default Port(s)

When a user creates a synthetic job, the Controller sends a request for the job with its configured frequency to the on-premises Synthetic Server. The synthetic jobs are then placed in a queue.

on-premises Synthetic Server

 HTTP(S)
  • 12101/12102
  • 10101/10102
The Synthetic Private Agent fetches the job requests from the Synthetic Server and then executes them on a browser using Selenium.

on-premises Synthetic Server

 HTTP(S) 10101/10102

The Synthetic Private Agent then sends the measurement results to the Synthetic Server.

on-premises Synthetic Server

 HTTP(S) 10101/10102

The on-premises Synthetic Server stores some data on file, and then processes and converts the data into a beacon, which is then transmitted to the EUM Server through the EUM API. The Synthetic Server also writes data to the EUM Server's MySQL database.

on-premises EUM Server

 HTTP(S)

7001/7002
JDBC 3388
The Controller polls the EUM Server for the measurement results and displays them in the Synthetic Sessions.

on-premises EUM Server

 HTTP(S) 7001/7002

Synthetic Hosted Agents Deployment

The following diagram shows the connections and data flow between the on-premises Synthetic Server, the SaaS EUM Server, the SaaS Synthetic Server, the Synthetic Hosted Agents, and the on-premises EUM Server.

Synthetic Server Connections

The following table lists and describes the traffic flow between the Synthetic Server and the other components.

Connection Source Destination Protocol Default Port(s)

When a user creates a synthetic job, the Controller sends a request for the job with its configured frequency to the on-premises Synthetic Server. The job requests are then placed in a queue.

on-premises Synthetic Server

 HTTP(S) 12101/12102

The on-premises Synthetic Server sends the job requests to the SaaS EUM Server.
SaaS EUM Server
HTTP(S) 7001/7002

The SaaS EUM Server forwards the requests to the SaaS Synthetic Server.
SaaS Synthetic Server
HTTP(S) 10001/10002

The Synthetic Hosted Agents fetch the job requests from the SaaS Synthetic Server and then executes them on a browser using Selenium.
SaaS Synthetic Server
WebSocket (encrypted) 16001

The Synthetic Hosted Agents send the measurement results to the SaaS Synthetic Server.
SaaS Synthetic Server
HTTP(S)

10001/10002

The SaaS Synthetic Server Feeder sends the measurement results to the on-premises Synthetic Client Feeder.
on-prem Synthetic Server
WebSocket (encrypted) 16101

The on-premises Synthetic Server stores some data on file, and then processes and converts the data into a beacon, which is then transmitted to the on-premises EUM Server through the EUM API. The on-prem Synthetic Server also writes data to the EUM Server's MySQL database.

on-premises EUM Server

 HTTP(S) 7001/7002
JDBC 3388

The Controller polls the on-premises EUM Server for the measurement results and displays them in the Synthetic Sessions.

on-premises EUM Server

 HTTP(S) 7001/7002