Set up PSA in Docker Engine

[SSEAL]

Good afternoon, Community,

I am in the process of setting up a PSA on a RHEL server and am a bit confused.

Does Docker engine need to be manually installed on the server before the actual PSA package is installed or does the install package automatically deploy Docker engine as stated in https://docs.appdynamics.com/appd/onprem/24.x/25.2/en/end-user-monitoring/synthetic-monitoring/insta...?

"You can set up PSA in the Docker engine using the automation script, which is available with the installation zip file. When you run the installation command, the script automatically builds the docker image and deploys PSA."

I'm getting conflicting information and as I read the opening paragraph of the online documentation, it looks like Docker engine is automatically installed.

Looking at the install commands, can I configure any of these commands after the initial installation?

/install_psa -e docker -v -u <Shepherd-URL> -a <EUM-account> -k <EUM-key> -c <location-code> -d <location-description> -t <location-name> -s <location-state> -o <location-country> -i <location-latitude> -g <location-longitude> -p <PSA-tag> -r <heimdall-replica-count> -z <agent-type> -m <chrome-agent_min/max-memory> -n <API-agent_min/max-memory> -x <chrome-agent_min/max-CPU> -y <API-agent_min/max-CPU> -w <heimdall_proxy_server>~<web_monitoring_proxy_server>~<api_monitoring_proxy_server> -B <bypass-proxy-domains> -q <ignite-persistence>

What is a Shepherd-URL?

What is chrome-agent?

Any information you may provide is greatly appreciated.

Thank you,

Stuart

[SSEAL]

Thank you so much for the assistance and confirmation.  It is extremely helpful.

I do have a few follow-on questions.

1.  What are the mandatory parameters that must have entries for the installer script to complete the installation?

2.  What are typical chrome-agent memory and cpu min/max parameters?

3.  What are the heimdall_proxy_server and web_monitoring_proxy_server and bypass-proxy-domains?

4.  Can these proxy server settings be bypassed if  using an F5 load balancer?

Thank you,

Stuart

[sainag_splunk · Accepted solution]

Hi @SSEAL, Based on the official AppDynamics documentation table you referenced, here are the answers to your questions:

  1. Mandatory Parameters (marked with * in the documentation table):

  According to the

  https://docs.appdynamics.com/appd/24.x/latest/en/end-user-monitoring/synthetic-monitoring/install-th...  the mandatory parameters are those marked with an asterisk (*) in the command usage table.

For the others, please refer: https://docs.appdynamics.com/appd/onprem/24.x/latest/en/end-user-monitoring/synthetic-monitoring/ins...

https://docs.appdynamics.com/appd/24.x/latest/en/end-user-monitoring/synthetic-monitoring/install-th...

[sainag_splunk]

Hi @SSEAL, You're absolutely right about the documentation - Docker Engine does NOT need to be manually installed. The PSA installation package includes an automation script that handles everything for you. When you run the installation command, the script will:

  - Automatically detect if Docker Engine is installed

  - Install Docker Engine if it's not present

  - Build the required Docker images

  - Deploy the PSA containers 

So you can start with a fresh RHEL server and let the PSA installer take care of the Docker setup completely.

Yes, most of those parameters can be modified after the initial installation, but there are some nuances.

Shepherd-URL: This is your AppDynamics Controller 

https://YOURURL>.saas.appdynamics.com/controller

Chrome-agent: 

This is the browser-based synthetic monitoring component that runs Chrome/Chromium to execute synthetic browser tests (like clicking through web applications). The memory and CPU parameters control how much system resources these browser tests can consume.

[SSEAL]

Thank you.  That got me started in the correct direction.  I appreciate all your help.

[sainag_splunk]

@SSEAL I'm glad it worked out for you. Please mark this as solved.