Refactored APM

Author: rcastley

content/en/s4r/60-apm/1-apm-service-map.md

@@ -0,0 +1,7 @@
+---
+title: 1. APM Service Map
+weight: 1
+---
+
+1. Arrived in APM from a RUM trace
+2. Validate workflow is **frontend:/cart/checkout**. Talk to the service map and how it is auto-generated

content/en/s4r/60-apm/2-apm-overview.md

@@ -0,0 +1,10 @@
+---
+title: 2. APM Overview
+weight: 2
+---
+
+1. Click on Overview
+2. Validate environment is the correct workshop one
+3. Ensure APM Overview is visible
+4. What can you conclude from the top services by error rate chart?
+5. Explain inferred services

content/en/s4r/60-apm/3-apm-explore.md

@@ -0,0 +1,8 @@
+---
+title: 3. APM Explore
+weight: 3
+---
+
+1. Click Explore, explain that compared to earlier you now see all services (including inferred)
+2. Click on the paymentservice, what can you conclude from the error rate chart?
+3. Is there a pattern to this error rate? We have a handy tool for that, tag spotlight.

content/en/s4r/60-apm/4-apm-tag-spotlight.md

@@ -0,0 +1,10 @@
+---
+title: 4. APM Tag Spotlight
+weight: 4
+---
+
+1. Click on tag spotlight
+2. Ensure **Show tags with no values** is off.
+3. What can you conclude from the data you are seeing? Which chart helped you come to this conclusion? (Answer is version).
+4. Click on v350.10 add to filter
+5. Return to explorer, click tag spotlight and clear all

content/en/s4r/60-apm/5-apm-service-breakdown.md

@@ -0,0 +1,7 @@
+---
+title: 5. APM Service Breakdown
+weight: 5
+---
+
+1. Click on the payment service and then from breakdown select **version**
+2. You can see all errors are due to v350.10

content/en/s4r/60-apm/6-apm-trace-analyzer.md

@@ -0,0 +1,7 @@
+---
+title: 6. APM Trace Analyzer
+weight: 6
+---
+
+1. Click on traces and sort the traces by duration descending by longest duration
+2. Select the 1st trace ensuring it has a long duration

content/en/s4r/60-apm/7-apm-waterfall.md

@@ -0,0 +1,10 @@
+---
+title: 7. APM Waterfall
+weight: 7
+---
+
+1. What can you conclude is going on from the waterfall? (Answer multiple attempts)
+2. Verify version is **v350.10** by looking at the metadata under tags.
+3. Conclusion ... we have an problem.
+4. Draw attention to related content ... TBC
+5. Click on Logs for trace XXXXXXX