Merge branch 'main' of https://github.com/splunk/observability-workshop

geoffhigginbottom · geoffhigginbottom · commit f219886f22b6 · 2023-12-01T10:59:09.000Z
diff --git a/content/en/s4r/5-rum/1-rum-dashboard.md b/content/en/s4r/5-rum/1-rum-dashboard.md
@@ -10,30 +10,32 @@ In Splunk Observability Cloud from the main menu, click on **RUM**. you arrive a
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Make sure you select your workshop by ensuring the drop-downs are set/selected as follows:
-  * The **Timeframe** is set to **-15m**.
+  * The **Time frame** is set to **-15m**.
   * The **Environment** selected is **[NAME OF WORKSHOP]-workshop**.
   * The **App** selected is **[NAME OF WORKSHOP]-store**.
   * The **Source** is set to **All**.
-* Next, click on the **[NAME OF WORKSHOP]-workshop** above the **Page Views / JavaScript Errors** chart.
-* This will bring up a dashboard view breaking down the metrics by **UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events** and compares them to the same metrics historically (1 hour by default). <!-- For more detailed information on the metrics collected by Splunk RUM see [**here**](https://docs.splunk.com/observability/en/gdi/get-data-in/rum/browser/rum-browser-data-model.html#rum-browser-data). -->
+* Next, click on the **[NAME OF WORKSHOP]-store** above the **Page Views / JavaScript Errors** chart.
+* This will bring up a new dashboard view breaking down the metrics by **UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events** and comparing them to historic metrics (1 hour by default).
+
 {{% /notice %}}
+
 ![RUM Dashboard](../images/rum-dashboard.png)
 
-* **UX Metrics**, This tab groups the *Web vitals* and other user interface metrics.
-* **Front-end Health**, This tab shows metrics regarding how the website behaved in the browsers.  
-* **Back-end Health**, In this tab you can find the metric related to overall network behavior.
-* **Custom Events**, In this tab we find metrics related to Custom Events added to the website by the developer to track behaviour.
+* **UX Metrics:** Page Views, Page Load and Web Vitals metrics.
+* **Front-end Health:** Breakdown of Javascript Errors and Long Task duration and count.
+* **Back-end Health:** Network Errors and Requests and Time to First Byte.
+* **Custom Events:** RED metrics (Rate, Error & Duration) for custom events.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Click through each of the tabs (**UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events**) and examine the data.
 
 {{< tabs >}}
 {{% tab title="Question" %}}
-**What chart clearly shows that there is an issue with the application?**
+**Which chart clearly shows that there is an issue with the application?**
 {{% /tab %}}
 {{% tab title="Answer" %}}
-**It is the *Custom Event Latency* chart in the *Custom Events* Tab,  Here you see long spikes for the function.**
+**It is the *Custom Event Latency* chart in the *Custom Events* Tab**
 {{% /tab %}}
 {{< /tabs >}}
 
diff --git a/content/en/s4r/5-rum/2-tag-spotlight.md b/content/en/s4r/5-rum/2-tag-spotlight.md
@@ -7,17 +7,13 @@ Click the **Custom Events** tab and have a look at the **Custom Event Latency**
 
 ![RUM Tag Spotlight](../images/rum-tag-spotlight.png)
 
-In this dashboard view, you are presented with all the tags associated with the RUM data. Tags are key-value pairs that are used to identify the data. In this case, the tags are automatically generated by the OpenTelemetry instrumentation. The tags are used to filter the data and to create the charts and tables. The Tag Spotlight view allows you to drill down into the data and find the root cause of the problem.
-
-Let's drill down on the RUM data we generated earlier.
+In this dashboard view, you are presented with all the tags associated with the RUM data. Tags are key-value pairs that are used to identify the data. In this case, the tags are automatically generated by the OpenTelemetry instrumentation. The tags are used to filter the data and to create the charts and tables. The Tag Spotlight view allows you to drill down into a user session.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Change the timeframe to **Last 1 hour**.
-* Click **Add Filters**, select **OS Version** then click **!=** and select **Splunk** and **RUMLoadGen**.
-* Click {{% button style="blue" %}}Apply Filter{{% /button %}}. Now, we only see the data we generated earlier.
+* Click **Add Filters**, select **OS Version**, click **!=** and select **Splunk** and **RUMLoadGen** then click the {{% button style="blue" %}}Apply Filter{{% /button %}} button.
 * Find the **Custom Event Name** tile, locate **PlaceOrder** and click on it, then click **Add to filter**.
-* Find the **City** tile, locate your city and click on it, then click **Add to filter**.
 * Notice the large spikes in the graph across the top.
 * Click on the **User Sessions** tab.
 * Click on the **Duration** heading twice to sort the sessions by duration (longest at the top).
diff --git a/content/en/s4r/5-rum/3-session-replay.md b/content/en/s4r/5-rum/3-session-replay.md
@@ -3,7 +3,7 @@ title: 3. Session Replay
 weight: 3
 ---
 
-In the **User Sessions** table, click on the top **Session ID**  with the longest **Duration***. (It should be over 10 seconds or longer), this will take you to the RUM Session view.
+In the **User Sessions** table, click on the top **Session ID**  with the longest **Duration** (over 20 seconds or longer), this will take you to the RUM Session view.
 
 A session is a collection of traces that correspond to the actions a single user takes when interacting with an application over a period of time. By default, a session lasts until 15 minutes have passed from the last event captured in the session. The maximum session duration is 4 hours.
 
diff --git a/content/en/s4r/5-rum/4-user-sessions.md b/content/en/s4r/5-rum/4-user-sessions.md
@@ -3,12 +3,12 @@ title: 4. User Sessions
 weight: 4
 ---
 
-Close the RUM Session Replay by clicking on the **X** in the top right corner. Here, we can see the custom event **PlaceOrder**. (If it is not immediately visible, type `PlaceOrder` in the search bar below thh Session replay section. Use the **⌵** & **⌃**  to find the longest one.) Notice the length of the span. This is the time it took to complete the order, not good!
+Close the RUM Session Replay by clicking on the **X** in the top right corner. Here, we can see the custom event **PlaceOrder** (if it is not immediately visible, type `PlaceOrder` in the search bar below the Session replay section). Note the length of the span, this is the time it took to complete the order, not good!
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Scroll down the page and you will see the **Tags** metadata (which is used in Tag Spotlight). After the tags, we come to the waterfall which shows the page objects loading (CSS, images, JavaScript etc.)
-* Scroll back up to the top of the metrics section and hover over the blue **APM** link (the one next to `Doc Fetch` with `/cart/checkout` at the end of the URL).
+* Scroll back up to the top of the metrics section and hover over the blue **APM** link (the one with `/cart/checkout` at the end of the URL).
 
 {{% /notice %}}
 
diff --git a/content/en/s4r/5-rum/images/multiple-apps.png b/content/en/s4r/5-rum/images/multiple-apps.png
diff --git a/content/en/s4r/6-apm/2-apm-service-dashboard.md b/content/en/s4r/6-apm/2-apm-service-dashboard.md
@@ -3,12 +3,10 @@ title: 2. APM Service Dashboard
 weight: 2
 ---
 
-APM dashboards present request, error, and duration (RED) metrics based on Monitoring MetricSets created from endpoint spans for your services, endpoints, and Business Workflows. They also present related host and Kubernetes metrics to help you determine whether problems are related to the underlying infrastructure.
+APM Service Dashboards provide request, error, and duration (**RED**) metrics based on Monitoring MetricSets created from endpoint spans for your services, endpoints, and Business Workflows. If you scroll down the dashboard you will also see the host and Kubernetes-related metrics which help you determine whether there are problems with the underlying infrastructure.
 
 ![Service Dashboard](../images/apm-service-dashboard.png)
 
-Note: *Need to explain some of the charts in the dashboard, and include using it the exercise*
-
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * In the **Request rate** text chart, click the **...** and select **Copy**. Note that you now have a **1** before the **+**  at the top right of the page, indicating you have a copied chart to the clipboard.
