Depending on the version of the AppDynamics Controller you are using, you may or may not be able download the Server Visibility agent from the Controller as shown here for Option 1.
Follow the steps seen below until you get to the Select the agent type for download section and if you do not see the Servers tile then you will need to use the Deploy Server Agent - Option 2 approach.
The advantage to using the Option 1 is that the agent will be pre-configured to connect to your controller VS using Option 2 will require that you edit the configuration of the agent to connect to the controller.
Use the URL below to login to your controller from your web browser.
http://[controller-vm-ip-address]:8090
1 . Select the Home tab at the top left of the screen.
2 . Select the Getting Started tab.
3 . Click Getting Started Wizard.
1 . Click on the Servers button.
1 . Leave the Platform Bundle set to Linux and 64-bit.
2 . Accept defaults for the Controller connection.
2 . Click Click Here to Download.
Save the Server Visibility Agent file to your file local workstation.
Your browser should prompt you to save the agent file to your local file system, similar to the following image (depending on your OS).
The process of uploading the Server agent file will vary depending on your workstation’s operating system. Copy the Server agent ZIP file either using SCP if your OS is MAC/Linux or using WinSCP if your OS is Windows.
Create the directory structure where you will unzip the Server agent zip file.
cd /opt/appdynamics
mkdir machineagent
Use the following commands to copy the Server Visibility agent zip file to the directory and unzip the file. The name of your Server Visibility agent file may be slightly different than the example below. (assumes you uploaded the zip file to the /tmp directory)
cp /tmp/machineagent-bundle-64bit-linux-20.4.0.2571.zip /opt/appdynamics/machineagent/
cd /opt/appdynamics/machineagent
unzip machineagent-bundle-64bit-linux-20.4.0.2571.zip
Use the following commands to start the Server Visibility agent and verify that it started.
cd /opt/appdynamics/machineagent/bin
nohup ./machine-agent &
ps -ef | grep machine
You should see output similar to the following image.
We’ll monitor the health of the server.