Application Performance Management - AppDynamics Self Service



In this screencast will cover how to get started with application performance management, using AppDynamics Self Service (http://www.appdynamics.com/freetrial).

Transcript:

In this screencast we’re going to go over how to get started with application performance management using AppDynamics Self-Service. In order to get started go to www.appdynamics.com/freetrial and fill out basic information in the form in order to provision a Self-Service account.

The first thing we’re going to need to do is validate our email address. Simple click on the link in the email and this will validate my account. Once my email is validated I’ll be able to choose a SaaS controller name. In this case I’ll make it ACME-testing. This will be our controller moving forward. Let’s see how fast we can get started instrumenting our application.

Now that I’ve validated my email address I can get started on the AppDynamics management server. If I want to access the AppDynamics management server moving forward I can simple refer to the SaaS URL at ACME-testing.saas.appdynamics.com.

Once we’re in the controller we can immediately start monitoring our application. In this case I want to get started with the App Agent for the Sun Java JVM and the Machine Agent so we can monitor CPU and memory utilization across all of our machines. Once these are finished downloading we can get started.

Now that we’ve downloaded the App Agent and the Machine Agent we can get started by installing them. Simple unzip the App Server Agent into /opt/appdynamics/java-agent and do the same with the Machine Agent. Simple unzip the Machine Agent into /opt/appdynamics/machine-agent.

Once we’re up and running we can go back to our app, in this case it’s a dropwizard-app. Now the only thing we need to do to start monitoring our app is instrument it with the Java Agent. In order to accomplish this we’ll simple add -javaagent and the path to our Java Agent, in this case /opt/appdynamics/java-agent/javaagent.jar and then we’ll run our server.

Now that we’ve instrumented our application with the AppDynamics Java Agent we can see the data is already starting to flow into the AppDynamics management server. From the dashboard, we can get a high level over view of the health of our application as well as some basic metrics, including how many calls have been made as well as the average response time. From here we can deep dive into each business transaction that’s been automatically discovered and we can also deep dive into the hardware to get CPU and memory information because we’ve installed the Machine Agent. If you’d like to find out more please visit us at http://www.appdynamics.com

source

Leave a Reply

Your email address will not be published.

Captcha loading...