Improved Synthetics flow

Author: rcastley

content/en/s4r/8-synthetics/1-synthetics-dashboard.md

@@ -3,32 +3,21 @@ title: 1. Synthetics Dashboard
 weight: 1
 ---
 
-In Splunk Observability Cloud from the main menu, click on **Synthetics**. Click on **All** or **Browser tests** to see the list of active tests:
+In Splunk Observability Cloud from the main menu, click on **Synthetics**. Click on **All** or **Browser tests** to see the list of active tests.
 
 During our investigation in the RUM section, we found there was an issue with the **Place Order** Transaction. Let's see if we can confirm this from the Synthetics test as well.
 
-In the **Search** box enter **Workshop Browser Test** and select the test for your workshop (your instructor will advise as to which one to select).
-
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* Make sure the page you are looking at is the result page for the **Workshop Browser Test for [NAME OF WORKSHOP]**
-* Under **Performance KPIs** set the Time Picker to **-1h** and hit enter.
-* From the **Location** drop-down select **Synthetic transactions**.
-* Looking at the dots, which transaction has a performance issue?
-* Next, change the Time Picker to **-15m** and hit enter.
-* Change the filtering so that only **Place Order** is visible by removing all other transactions from the drop-down.
+* In the **Search** box enter **Workshop Browser Test** and select the test for your workshop (your instructor will advise as to which one to select).
+* Under **Performance KPIs** set the Time Picker to **-30m** and hit enter.
+* Click on **Location** and from the drop-down and select **Page**. The next filter will be populated with the pages that are part of the test.
+* Click on **Duration** and deselect **Duration** and then select **First byte time**.
   ![Transaction Filter](../images/synthetics-transaction-filter.png)
-* As you move your mouse pointer horizontally across the chart a vertical line will appear showing the duration and the time of the test.
-* What can you conclude about the relation of the dots and the red **X** at the bottom?
-* Change the filter to just *Keep Browsing*, the dots will change both pattern and color.
-* Select a successful test dot. (One that has no red X beneath it). If there are multiple tests in that time range you will be presented with a list of tests. Pick one that is 20 seconds or longer and results in ✅ Success.
-  ![Duration - Place Order](../images/duration-place-order.png)
+* Look at the legend and note the color of **First byte time - Page 4**.
+* Select the highest data point for **First byte time - Page 4**.
+* A new pane will slide in from the right. Note the time at the top of the pane. Find this time in the list and click on it.
+  ![Multiple Runs](../images/synthetics-multiple-runs.png)
 {{% /notice %}}
 
-![Results](../images/select-result.png)
-
-This will take you to the Synthetic Test Details or Waterfall. If the Waterfall has a Red Banner like this on top:
-
-![error](../images/run-result-error.png?classes=left)
-
-You accidentally picked a test that had an error, it timed out. (This can happen as new tests are added and the UI just refreshed). In that case, use the browser back button and try again.
+You will now be taken to the **Run results** for this particular test run.

content/en/s4r/8-synthetics/2-synthetics-detail.md

@@ -13,7 +13,7 @@ Right now we are looking at the result of a single Synthetic Browser Test. This
 4. **Synthetic transactions:**  List of the Synthetic transactions that made up the interaction with the site
 5. **Waterfall chart**  The waterfall chart is a visual representation of the interaction between the test runner and the site being tested.
 
-By default, Splunk Synthetics provides screenshots and video capture of the test. This is useful for debugging issues. You can see, for example, slow loading of large images, the slow rendering of a page etc.
+By default, Splunk Synthetics provides screenshots and video capture of the test. This is useful for debugging issues. You can see, for example, the slow loading of large images, the slow rendering of a page etc.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 

content/en/s4r/8-synthetics/3-synthetics-to-apm.md

@@ -9,10 +9,8 @@ We now should have a view similar to the one below.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* In the waterfall find the second call out to **POST checkout**.
-* Click on the **>** button in front of it to drop open the metadata section.
-* Verify that the credit card information is passed to the service.
-* Close the Meta Data view and confirm you have the same view as above.
+* In the waterfall find an entry that starts with **POST checkout**.
+* Click on the **>** button in front of it to drop open the metadata section. Observe the metadata that is collected, note the **Server-Timing** header. This header is what allows us to correlate the test run to a back-end trace.
 * Click on the blue {{% icon icon="link" %}} **APM** link on the **POST checkout** line in the waterfall.
 {{% /notice %}}