Markdown linting

Author: rcastley

content/en/ninja-workshops/15-AppDynamics-Workshop/1-application-performance-monitoring/1-download-agent/_index.md renamed to content/en/ninja-workshops/15-appd-workshop/1-application-performance-monitoring/1-download-agent/_index.md

@@ -1,31 +1,32 @@
 ---
-title: Download Java Agent
+title: 1. Download Java Agent
 weight: 1
 description: In this exercise you will access your AppDynamics Controller from your web browser and download the Java APM agent from there.
 ---
 In this exercise you will access the AppDynamics Controller from a web browser and download the Java APM agent from there.
 
 ## Login to the Controller
-Log into the [AppDynamics SE Lab Controller](https://se-lab.saas.appdynamics.com/controller/) using your Cisco credentials. 
+
+Log into the [AppDynamics SE Lab Controller](https://se-lab.saas.appdynamics.com/controller/) using your Cisco credentials.
 
 ## Configure your Application
 
 1. Select **Overview** on the left navigation panel
 2. Click on **Getting Started** tab
-3. Click on **Getting Started Wizard** button 
+3. Click on **Getting Started Wizard** button
 
-![Getting Started Wizard](images/agent-wizard-rz.png)  
+![Getting Started Wizard](images/agent-wizard-rz.png)
 
-Select the Java Application Type 
+Select the Java Application Type
 
 ![Java Application](images/select-java-rz.png)
 
 ## Download the Java Agent
 
-1. Select the **Sun/JRockit - Legacy** for the JVM type 
+1. Select the **Sun/JRockit - Legacy** for the JVM type
 2. Accept defaults for the Controller connection.
 3. Under **Set Application and Tier**, select **Create a new Application:**
-4. Enter **Supercar-Trader-YOURINITIALS** as the application name. 
+4. Enter **Supercar-Trader-YOURINITIALS** as the application name.
 5. Enter **Web Portal** for the new Tier
 6. Enter **Web-Portal_Node-01** for the Node Name
 7. Click **Continue**
@@ -39,8 +40,6 @@ The application name must be unique, make sure to append your initials or add a
 
 ![Agent Configuration2](images/java-agent-config2-rz.png)
 
-
-Your browser should prompt you that the agent is being downloaded to your local file system. Make sure to take note of where the file was downloaded to and the full name of it. 
+Your browser should prompt you that the agent is being downloaded to your local file system. Make sure to take note of where the file was downloaded to and the full name of it.
 
 ![Agent Bundle](images/agent-bundle-rz.png)
-

content/en/ninja-workshops/15-AppDynamics-Workshop/1-application-performance-monitoring/1-download-agent/images/agent-bundle-rz.png renamed to content/en/ninja-workshops/15-appd-workshop/1-application-performance-monitoring/1-download-agent/images/agent-bundle-rz.png

@@ -1,5 +1,5 @@
 ---
-title: Install the Java Agent
+title: 2. Install the Java Agent
 weight: 2
 description: In this exercise you will SSH into your server and proceed to install the Java agent.
 ---
@@ -12,29 +12,35 @@ In this exercise you will perform the following actions:
 - Modify the Apache Tomcat startup script to add the Java agent
 
 ## Upload Java Agent to Application VM
+
 By this point you should have received the information regarding the EC2 instance that you will be using for this workshop. Ensure you have the IP address of your EC2 instance, username and password required to ssh into the instance .
 
 On your local machine, open a terminal window and change into the directory where the java agent file was downloaded to. Upload the file into the EC2 instance using the following command. This may take some time to complete.
 
-* Update the IP address or public DNS for your instance.
-* Update the filename to match your exact version.
+- Update the IP address or public DNS for your instance.
+- Update the filename to match your exact version.
 
 {{< tabs >}}
 {{% tab title="Command" %}}
+
 ``` bash
 cd ~/Downloads
 scp -P 2222 AppServerAgent-22.4.0.33722.zip [email protected]:/home/splunk
 ```
+
 {{% /tab %}}
 {{% tab title="Example Output" %}}
+
 ``` bash
 ([email protected]) Password:
 AppServerAgent-22.4.0.33722.zip                                                                    100%   22MB 255.5KB/s   01:26
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
-## Unzip the Java Agent 
+## Unzip the Java Agent
+
 SSH into your EC2 instance using the instance and password assigned to you by the instructor.
 
 ``` bash
@@ -61,28 +67,30 @@ There are three primary ways to set the configuration properties of the Java age
 3. Properties within the ```controller-info.xml``` file.
 {{% /notice %}}
 
-
 ## Add the Java Agent to the Tomcat Server
 
-First we want to make sure that the Tomcat server is not running 
+First we want to make sure that the Tomcat server is not running
 
 ``` bash
 cd /usr/local/apache/apache-tomcat-9/bin
 ./shutdown.sh
 ```
 
-We will now modify the catalina script to set an environment variable with the java agent. 
+We will now modify the catalina script to set an environment variable with the java agent.
 
 ``` bash
 cd /usr/local/apache/apache-tomcat-9/bin
 nano catalina.sh
-``` 
+```
+
 Add the following line at 125 (after the initial comments) & save the file
+
 ``` bash
 export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/opt/appdynamics/javaagent/javaagent.jar"
-``` 
+```
 
 Restart the server
+
 ``` bash
 ./startup.sh
 ```
@@ -91,11 +99,14 @@ Validate that the Tomcat server is running, this can take a few minutes
 
 {{< tabs >}}
 {{% tab title="Command" %}}
+
 ``` bash
 curl localhost:8080
 ```
+
 {{% /tab %}}
 {{% tab title="Example Output" %}}
+
 ``` bash
 <!DOCTYPE html>
 <html lang="en">
@@ -110,5 +121,6 @@ curl localhost:8080
         <div id="wrapper"
 ....
 ```
+
 {{% /tab %}}
 {{< /tabs >}}

content/en/ninja-workshops/15-AppDynamics-Workshop/1-application-performance-monitoring/1-download-agent/images/agent-wizard-rz.png renamed to content/en/ninja-workshops/15-appd-workshop/1-application-performance-monitoring/1-download-agent/images/agent-wizard-rz.png

@@ -1,5 +1,5 @@
 ---
-title: Generate Application Load
+title: 3. Generate Application Load
 weight: 3
 description: In this section you will install the sample application and begin the load generation
 ---
@@ -15,23 +15,26 @@ The sample application home page is accessible through your web browser with a U
 
 ```bash
 http://[ec2-ip-address]:8080/Supercar-Trader/home.do
-``` 
+```
 
 You should be able to see the home page of the Supercar Trader application.
 ![Supercar Trade Home Page](images/SuperCarHomePage-rz.png)
 
 ## Start the Load Generation
 
-SSH into your ec2 instance and start the load generation. It may take a few minutes for all the scripts to run. 
+SSH into your ec2 instance and start the load generation. It may take a few minutes for all the scripts to run.
 
 {{< tabs >}}
 {{% tab title="Command" %}}
+
 ``` bash
 cd /opt/appdynamics/lab-artifacts/phantomjs
 ./start_load.sh
 ```
+
 {{% /tab %}}
 {{% tab title="Example Output" %}}
+
 ``` bash
 Cleaning up artifacts from previous load...
 Starting home-init-01
@@ -70,32 +73,33 @@ Starting request-error-01
 Starting mem-leak-insurance
 Finished starting load generator scripts                                                                100%   22MB 255.5KB/s   01:26
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
 ## Confirm transaction load in the Controller
 
 If you still have the Getting Started Wizard open in your web browser, you should see that the agent is now connected and that the Controller is receiving data.
+
 ![Agent Connected](images/agent_connected.png)
-Click **Continue** and you will be taken to the **Application Flow Map** (you can jump to the Flow Map image below).
 
+Click **Continue** and you will be taken to the **Application Flow Map** (you can jump to the Flow Map image below).
 
 If you previously closed the Controller browser window, log back into the Controller.
 
 1. From the Overview page (Landing Page). Click on the **Applications** tab on the left navigation panel.
 
-![Controller Overview Page](images/ControllerOverviewPage.png)  
+    ![Controller Overview Page](images/ControllerOverviewPage.png)
 
-2. Within the **Applications** page you can manually search for your application or you can use the search bar in the top right corner to narrow down your search. 
+2. Within the **Applications** page you can manually search for your application or you can use the search bar in the top right corner to narrow down your search.
 
-![Applications Search](images/ApplicationsSearch.png)   
+    ![Applications Search](images/ApplicationsSearch.png)
 
 Click in your application's name, this should bring you into the **Application Flow Map**, you should see all the application components appear after twelve minutes.
 
 If you don’t see all the application components after twelve minutes, try waiting a few more minutes and refresh your browser tab.
- 
-![FlowMap](images/SuperCarTrader_FlowMap-rz.png)  
 
+![FlowMap](images/SuperCarTrader_FlowMap-rz.png)  
 
 During the agent download step we assigned the Tier name and Node name for the Tomcat server.
 
@@ -110,29 +114,34 @@ To see the JVM startup parameters used for each of the four services that were d
 
 {{< tabs >}}
 {{% tab title="Command" %}}
+
 ``` bash
 ps -ef | grep appdynamics.agent.tierName
-``` 
+```
+
 {{% /tab %}}
 {{% tab title="Loadgen Output" %}}
+
 ``` bash
 splunk     47131   46757  3 15:34 pts/1    00:08:17 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -javaagent:/opt/appdynamics/javaagent/javaagent.jar -Dappdynamics.controller.hostName=se-lab.saas.appdynamics.com -Dappdynamics.controller.port=443 -Dappdynamics.controller.ssl.enabled=true -Dappdynamics.agent.applicationName=Supercar-Trader-AppD-Workshop -Dappdynamics.agent.tierName=Api-Services -Dappdynamics.agent.nodeName=Api-Services_Node-01 -Dappdynamics.agent.accountName=se-lab -Dappdynamics.agent.accountAccessKey=hj6a4d7h2cuq -Xms64m -Xmx512m -XX:MaxPermSize=256m supercars.services.api.ApiService
 splunk     47133   46757  2 15:34 pts/1    00:08:11 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -javaagent:/opt/appdynamics/javaagent/javaagent.jar -Dappdynamics.controller.hostName=se-lab.saas.appdynamics.com -Dappdynamics.controller.port=443 -Dappdynamics.controller.ssl.enabled=true -Dappdynamics.agent.applicationName=Supercar-Trader-AppD-Workshop -Dappdynamics.agent.tierName=Inventory-Services -Dappdynamics.agent.nodeName=Inventory-Services_Node-01 -Dappdynamics.agent.accountName=se-lab -Dappdynamics.agent.accountAccessKey=hj6a4d7h2cuq -Xms64m -Xmx512m -XX:MaxPermSize=256m supercars.services.inventory.InventoryService
 splunk     47151   46757  1 15:34 pts/1    00:04:58 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -javaagent:/opt/appdynamics/javaagent/javaagent.jar -Dappdynamics.controller.hostName=se-lab.saas.appdynamics.com -Dappdynamics.controller.port=443 -Dappdynamics.controller.ssl.enabled=true -Dappdynamics.agent.applicationName=Supercar-Trader-AppD-Workshop -Dappdynamics.agent.tierName=Insurance-Services -Dappdynamics.agent.nodeName=Insurance-Services_Node-01 -Dappdynamics.agent.accountName=se-lab -Dappdynamics.agent.accountAccessKey=hj6a4d7h2cuq -Xms64m -Xmx68m -XX:MaxPermSize=256m supercars.services.insurance.InsuranceService
 splunk     47153   46757  3 15:34 pts/1    00:08:17 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -javaagent:/opt/appdynamics/javaagent/javaagent.jar -Dappdynamics.controller.hostName=se-lab.saas.appdynamics.com -Dappdynamics.controller.port=443 -Dappdynamics.controller.ssl.enabled=true -Dappdynamics.agent.applicationName=Supercar-Trader-AppD-Workshop -Dappdynamics.agent.tierName=Enquiry-Services -Dappdynamics.agent.nodeName=Enquiry-Services_Node-01 -Dappdynamics.agent.accountName=se-lab -Dappdynamics.agent.accountAccessKey=hj6a4d7h2cuq -Xms64m -Xmx512m -XX:MaxPermSize=256m supercars.services.enquiry.EnquiryService
 splunk    144789   46722  0 20:09 pts/1    00:00:00 grep --color=auto appdynamics.agent.tierName
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
 Once all of the components appear on the flow map, you should see an HTTP cloud icon that represents the three HTTP backends called by the Insurance-Services Tier.
 
 Ungroup the the three HTTP backends by following these steps.
+
 1. Right click the HTTP cloud icon labeled 3 HTTP backends
 2. From the drop down menu, select Ungroup Backends
 
-![Ungroup Http](images/ungroup-http-rz.png)   
+![Ungroup Http](images/ungroup-http-rz.png)
 
-Once the HTTP backends have been ungrouped, you should see all three HTTP backends as shown in the following image.  
+Once the HTTP backends have been ungrouped, you should see all three HTTP backends as shown in the following image.
 
-![Ungroup flow](images/ungrouped_flow-rz.png) 
+![Ungroup flow](images/ungrouped_flow-rz.png)