On this page:
Search the On-Premises Synthetic Server topics:
The Synthetic Server dispatches and processes requests and depends on Synthetic Agents for executing and reporting measurements.
The Synthetic Server receives synthetic job requests from the Controller and then the jobs are fetched from the Synthetic Services by the Synthetic Agents. Once the measurement results are received from the Synthetic Agents, the Synthetic Server stores, processes, and transmits the results to the EUM Server.
To set up a complete on-premises Synthetic Server deployment, therefore, you need to:
- Install the on-premises Controller or prepare an in-service Controller to work with the EUM Server.
- Install the on-premises Events Service and configure it to work with your on-premises Controller.
- Install the on-premises EUM Server and configure it to work with your Events Service and Controller.
- Install the on-premises Synthetic Server and configure it to work with the EUM Server and the Controller.
- Install Synthetic Private Agents.
- Connect the Synthetic Private Agents to the on-premises Synthetic Server.
- Monitor the Synthetic Server (Recommended)
Synthetic Server Components
The Synthetic Server consist of two services. The first service is the Synthetic Scheduler, which is cron-like service that sends job requests at configured intervals. The Synthetic Scheduler also handles the CRUD operations for jobs as well as managing the events generated for synthetic warnings and errors that occur in the measurement results.
The second service is Synthetic Shepherd. This service manages and dispatches jobs to the synthetic agents. In addition, the Synthetic Shepherd saves the measurement results to the filesystem and sends a beacon containing the data to the Synthetic Scheduler.
After receiving the beacon from Synthetic Shepherd, the Synthetic Scheduler validates the beacons, triggers warning and error events if needed, and forwards the beacon to the EUM Server.
Summary of Synthetic Server and Agents
The table below summarizes the function and ports used by each service and the Synthetic Agent:
|Default Ports (HTTP/HTTPS)|
|Synthetic Agents||The Synthetic Agents do not listen to any ports. They only temporarily open internal random ports to fetch job requests from the Synthetic Shepherd and to send the measurement results of executed jobs to the Synthetic Shepherd.|
Synthetic Service Data
The Synthetic Server stores data on the filesystem of the host machine and data in the EUM Server's MySQL database. The table below lists the types of data and the storage location.
|Data Storage Format||Data||Location of Data Storage|
|MySQL||EUM Server's MySQL database|
|File System||Host machine of Synthetic Server|
Synthetic Server Deployment Architecture
The following diagram shows the connections and data flow between the on-premises Synthetic Server and the EUM Server and Synthetic Agents. For information about the other AppDynamics platform components, see Platform Components and Platform Connections.
Synthetic Server Connections
The following table lists and describes the traffic flow between the Synthetic Server and the other components.
The Controller sends a request to start a synthetic job to the Synthetic Server. The synthetic jobs are then placed in a queue.
|The Synthetic Agent fetches the job requests from the Synthetic Server and then executes them on a browser using Selenium.||Synthetic Server||HTTP(S)||10101/10102|
|The Synthetic Server stores some data on file and processes/converts the data into a beacon, which is then transmitted to the EUM Server through the EUM API.||EUM Server||HTTP(S)|
|The Controller polls the EUM Server for the measurement results and displays them in the Synthetic Sessions.||EUM Server||HTTP(S)||7001/7002|