Instructions for the AppDynamics Lite ami



Download 17.56 Kb.
Date23.05.2017
Size17.56 Kb.
TypeInstructions
Usage Instructions for the AppDynamics Lite AMI
The Community Amazon Machine Image (AMI) for AppDynamics Lite is:

 ami-37f8335e.

Users who wish to try out AppDynamics Lite should launch an instance using this AMI. 

While selecting the parameters for launch, users should choose the Instance Type as c1.medium and create a new key pair unless one already exists for that user. 

Once the instance is running, the user may ssh into the new instance using:

1. The DNS name for that instance

2. the .pem (key pair) file from above 

3. the user ec2-user 

as shown below:

[~]# ssh -i pranta-keypair2.pem ec2-user@ec2-107-22-18-12.compute-1.amazonaws.com

Last login: Thu Dec  1 18:02:19 2011 from 99-45-174-83.lightspeed.sntcca.sbcglobal.net

       __|  __|_  )  Amazon Linux AMI

       _|  (     /     Beta

      ___|\___|___|

 

See /usr/share/doc/system-release-2011.02 for latest release notes. :-)



[ec2-user@ip-10-66-83-89 ~]$ 

 

The newly launched AppDynamics Lite instance contains both the AppServerAgentLite and the LiteViewer. For more information on these components, please visit http://litedocs.appdynamics.com,



 

There are specifically 2 usage patterns and these are described below.



  • Usage-Pattern-1: In this pattern, the user deploys the application to be monitored onto the AWS instance above that contains the AppDynamics components and instruments that application using the AppServerAgentLite available there.






  • Usage-Pattern-2: In this pattern, the user continues to run the application wherever it is currently running, but zips up and downloads the AppDynamics AppServerAgentLite from the AWS instance and copies it to the machine where the application is running. The user then attaches the AppServerAgentLite to the application on a separate machine and points that agent to point to the LiteViewer running on the AWS instance above. To achieve this zipping up and copying of the agent, the following steps need to be followed:


Step 1: Zip up the agent into a zip file






[ec2-user@ip-10-66-83-89 ~]$ pwd

/home/ec2-user

[ec2-user@ip-10-66-83-89 ~]$ ls

AppServerAgentLite  LiteViewer  monitoredServers  start-liteviewer  stop-liteviewer  user-data

[ec2-user@ip-10-66-83-89 ~]$ zip -r AppServerAgentLite.zip AppServerAgentLite/

  adding: AppServerAgentLite/ (stored 0%)

  adding: AppServerAgentLite/javaagent.jar (deflated 20%)

  adding: AppServerAgentLite/readme.txt (deflated 56%)

  adding: AppServerAgentLite/logs/ (stored 0%)

  adding: AppServerAgentLite/logs/ip-10-114-30-8.ec2.internal/ (stored 0%)

  adding: AppServerAgentLite/logs/ip-10-114-30-8.ec2.internal/ByteCodeTransformer.2011_07_12__22_30_39.0.log (deflated 96%)

  adding: AppServerAgentLite/logs/ip-10-114-30-8.ec2.internal/REST.log (stored 0%)

  adding: AppServerAgentLite/logs/ip-10-114-30-8.ec2.internal/agent.log (deflated 80%)

  adding: AppServerAgentLite/logs/ip-10-114-30-8.ec2.internal/BusinessTransactions.log_2011_07_12__10_30_38.log (deflated 55%)

  adding: AppServerAgentLite/logs/ip-10-114-57-188/ (stored 0%)

  adding: AppServerAgentLite/logs/ip-10-114-57-188/REST.log (stored 0%)

  adding: AppServerAgentLite/logs/ip-10-114-57-188/agent.log (deflated 79%)

  adding: AppServerAgentLite/logs/ip-10-114-57-188/BusinessTransactions.log_2011_06_21__12_05_10.log (deflated 54%)

  adding: AppServerAgentLite/logs/ip-10-114-57-188/ByteCodeTransformer.2011_06_21__00_05_11.0.log (deflated 95%)

  adding: AppServerAgentLite/conf/ (stored 0%)

  adding: AppServerAgentLite/conf/logging/ (stored 0%)

  adding: AppServerAgentLite/conf/logging/log4j.xml (deflated 78%)

  adding: AppServerAgentLite/conf/logging/log4j.dtd (deflated 70%)

  adding: AppServerAgentLite/lib/ (stored 0%)

  adding: AppServerAgentLite/lib/singularity-log4j.jar (deflated 12%)

  adding: AppServerAgentLite/lib/tp/ (stored 0%)

  adding: AppServerAgentLite/lib/tp/commons-logging-adapters-1.1.1.jar (deflated 9%)

  adding: AppServerAgentLite/lib/tp/asm-3.1.jar (deflated 8%)

  adding: AppServerAgentLite/lib/tp/commons-io-1.4.jar (deflated 10%)

  adding: AppServerAgentLite/lib/tp/servlet-api-2.5-6.1.3.jar (deflated 6%)

  adding: AppServerAgentLite/lib/tp/commons-httpclient-3.1.jar (deflated 8%)

  adding: AppServerAgentLite/lib/tp/commons-fileupload-1.2.1.jar (deflated 14%)

  adding: AppServerAgentLite/lib/tp/commons-logging-1.1.1.jar (deflated 8%)

  adding: AppServerAgentLite/lib/tp/commons-math-2.1.jar (deflated 11%)

  adding: AppServerAgentLite/lib/tp/commons-logging-api-1.1.1.jar (deflated 8%)

  adding: AppServerAgentLite/lib/tp/commons-codec-1.3.jar (deflated 11%)

  adding: AppServerAgentLite/lib/tp/singularity-xerces.jar (deflated 12%)

  adding: AppServerAgentLite/lib/appagent.jar (deflated 12%)

Step 2: Exit the AWS instance

[ec2-user@ip-10-66-83-89 ~]$ exit

logout

Connection to ec2-107-22-18-12.compute-1.amazonaws.com closed.



Step 3: scp the agent zip file, using the same .pem file used for ssh, into the machine where the application is running. Then follow the same instructions of attaching the agent to the application as documented in http://litedocs.appdynamics.com.

[~]# scp -i pranta-keypair2.pem ec2-user@ec2-107-22-18-12.compute-1.amazonaws.com:/home/ec2-user/AppServerAgentLite.zip .



AppServerAgentLite.zip                                                                               100% 5644KB 235.2KB/s   00:24    

[~]# 

Download 17.56 Kb.

Share with your friends:




The database is protected by copyright ©ininet.org 2020
send message

    Main page