Skip to content

Commit c5a84ba

Browse files
committed
spit and polish
1 parent 82c1f86 commit c5a84ba

File tree

1 file changed

+19
-12
lines changed

1 file changed

+19
-12
lines changed

content/en/s4r/5-rum/1-rum-dashboard.md

Lines changed: 19 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,17 +7,16 @@ In Splunk Observability Cloud from the main menu, click on **RUM**. you arrive a
77

88
![multiple apps](../images/multiple-apps.png)
99

10-
Make sure you select your workshop by ensuring the drop-downs are set/selected as follows:
11-
12-
* The **Timeframe** is set to **-15m**.
13-
* The **Environment** selected is **[NAME OF WORKSHOP]-workshop**.
14-
* The **App** selected is **[NAME OF WORKSHOP]-store**.
15-
* The **Source** is set to **All**.
16-
17-
Next, click on the **[NAME OF WORKSHOP]-workshop** above the **Page Views / JavaScript Errors** chart.
18-
19-
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). -->
10+
{{% notice title="Exercise" style="green" icon="running" %}}
2011

12+
* Make sure you select your workshop by ensuring the drop-downs are set/selected as follows:
13+
* The **Timeframe** is set to **-15m**.
14+
* The **Environment** selected is **[NAME OF WORKSHOP]-workshop**.
15+
* The **App** selected is **[NAME OF WORKSHOP]-store**.
16+
* The **Source** is set to **All**.
17+
* Next, click on the **[NAME OF WORKSHOP]-workshop** above the **Page Views / JavaScript Errors** chart.
18+
* 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). -->
19+
{{% /notice %}}
2120
![RUM Dashboard](../images/rum-dashboard.png)
2221

2322
* **UX Metrics**, This tab groups the *Web vitals* and other user interface metrics.
@@ -27,7 +26,15 @@ This will bring up a dashboard view breaking down the metrics by **UX Metrics**,
2726

2827
{{% notice title="Exercise" style="green" icon="running" %}}
2928

30-
* Click through each of the tabs (**UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events**)
31-
* Find the chart that clearly shows there is an issue with the application. Hint, it's a Custom Event.
29+
* Click through each of the tabs (**UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events**) and examine the data.
30+
31+
{{< tabs >}}
32+
{{% tab title="Question" %}}
33+
**What chart clearly shows that there is an issue with the application?**
34+
{{% /tab %}}
35+
{{% tab title="Answer" %}}
36+
**It is the *Custom Event Latency* chart in the *Custom Events* Tab, Here you see long spikes for the function.**
37+
{{% /tab %}}
38+
{{< /tabs >}}
3239

3340
{{% /notice %}}

0 commit comments

Comments
 (0)