You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Note, On the Synthetic Tests Page, the first pane will show the performance of your site for the last day, 8 days and 30 days. As shown in the screenshot above, only if a test started far enough in the past, the corresponding chart will contain data. For the workshop, this depends on when it was created for you and if there is any data.
29
-
* In the Performance KPI Drop down box, change the time from the default 4 hours to last hour.
29
+
* In the Performance KPI drop-down, change the time from the default 4 hours to the 1 last hour.
30
30
* What can you conclude from the dotted chart, how often are these tests run, and from where?
Lets look at some other parts of th UI like the *Information Pane* on the right of the navigator or the *Related Content Pane* at the bottom.
10
+
Let's look at some other parts of the UI like the *Information Pane* on the right of the navigator or the *Related Content Pane* at the bottom.
11
11
12
-
First lets look at the *Information Pane*, this pane provides alert information, info on detected services and shows the Meta Data related to the object you're looking at.
12
+
First, let's look at the *Information Pane*, this pane provides alert and detected services information and the metadata related to the object you're looking at.
Meta Data is sent along with the metrics and is very useful to identify trends when looking into issues. An example could be a pod failing when deployed on a specific Operating System.
16
+
Meta Data is sent along with the metrics and is very useful for identifying trends when looking into issues. An example could be a pod failing when deployed on a specific Operating System.
* Can you identify what the Operating System and Architecture is what our node is running using the Meta Data?
20
+
* Can you identify the Operating System and Architecture of the node from the metadata?
21
21
22
22
{{% /notice %}}
23
23
24
-
As we have seen in the previous exercise, these fields are very useful to filter the view in charts and Navigators down to a specific subset of metrics we are interested in.
24
+
As we have seen in the previous exercise, these fields are very useful for filtering the view in charts and Navigators down to a specific subset of metrics we are interested in.
25
25
26
-
An other feature of the Splunk Observability UI, is what we call *Related content*.
26
+
Another feature in the UI is **Related content**.
27
27
28
28
{{% notice title=" Related Content" style="info" %}}
29
-
The Splunk Observability User Interface will attempt to show you additional information that is related to what you're actively looking at.
29
+
The Splunk Observability User Interface will attempt to show you additional information that is related to what you're actively looking at.
30
30
A good example of this is the Kubernetes Navigator showing you related Content tiles in the information Pane for the services found running on this node.
31
31
32
32
{{% /notice %}}
33
33
34
-
In the *Information pane* you should see two tiles for services detected, the two databases used by our e-commerce application. Let's use this *Related Content*.
34
+
In the **Information Pane**, you should see two tiles for services detected, the two databases used by our e-commerce application. Let's use this **Related Content**.
* First make sure you no longer have a filter for the development namespace active. (Simply click on the **x** to remove it from the Filter Pane) as there are no databases in the Development Name space.
38
+
* First, make sure you no longer have a filter for the development namespace active. (Simply click on the **x** to remove it from the Filter Pane) as there are no databases in the Development Namespace.
39
39
* Hoover on the *Redis* tile, and click on the {{% button style="blue" %}}Goto all my Redis instances{{% /button %}} button
40
40
* The Navigator view should change to the overall Redis instances view.
41
-
* Select the the instance running on your cluster. (Click on the blue link, named *redis-[the name of your workshop]*, in the Redis Instances pane).
41
+
* Select the the instance running on your cluster. (Click on the blue link, named **redis-[the name of your workshop]**, in the Redis Instances pane).
42
42
* We should now see just the information for your Redis Instance & there should also be an *Information Pane*.
43
43
* Again we see Meta Data, but we also see that UI is showing in the *Related Content* tiles that this Redis Server runs in a Container running on Kubernetes.
44
44
* Let's verify that by clicking on the *Kubernetes* Tile.
@@ -47,4 +47,4 @@ In the *Information pane* you should see two tiles for services detected, the tw
47
47
48
48
{{% /notice %}}
49
49
50
-
This completes the tour of the Splunk Observability SuiteUI. Let's go an look at our E-commerce site and do some shopping in the next page.
50
+
This completes the tour of Splunk Observability Cloud. Let's go and look at our e-commerce site and do some shopping.
The screenshot above shows the main part of the Kubernetes navigator. It will show all the clusters & their nodes that send metrics to the Splunk Observability Suite, and the first row of charts that show cluster-based Metrics. In the workshop, you will mostly see single-node Kubernetes clusters.
30
+
The screenshot above shows the main part of the Kubernetes navigator. It will show all the clusters & their nodes that send metrics to Splunk Observability Cloud, and the first row of charts that show cluster-based Metrics. In the workshop, you will mostly see single-node Kubernetes clusters.
31
31
32
-
Before we dive deeper, let's make sure we are looking at our own cluster.
32
+
Before we dive deeper, let's make sure we are looking at our cluster.
Copy file name to clipboardExpand all lines: content/en/s4r/3-initial-tour/_index.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,4 +5,10 @@ weight: 3
5
5
archetype: chapter
6
6
---
7
7
8
-
A walkthrough of the various components of Splunk Observability Cloud showing you how to easily navigate the 5 main components:- **APM, RUM, Log Observer, Synthetics and Infrastructure**.
8
+
A walkthrough of the various components of Splunk Observability Cloud showing you how to easily navigate the 5 main components:
Copy file name to clipboardExpand all lines: content/en/s4r/5-rum/1-rum-dashboard.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,10 @@ tags: RUM
6
6
7
7
In Splunk Observability Cloud from the main menu, click on **RUM**. From the drop-downs ensure the following is set/selected:
8
8
9
-
* Timeframe is set to **-15m**.
10
-
* Environment selected is **[NAME OF WORKSHOP]-workshop**.
11
-
* App selected is **[NAME OF WORKSHOP]-store**.
12
-
* Source is set to **All**.
9
+
*The **Timeframe** is set to **-15m**.
10
+
*The **Environment** selected is **[NAME OF WORKSHOP]-workshop**.
11
+
*The **App** selected is **[NAME OF WORKSHOP]-store**.
12
+
*The **Source** is set to **All**.
13
13
14
14
This view has already been covered in the short introduction earlier. Next, click on the **[NAME OF WORKSHOP]-workshop** above the **Page Views / JavaScript Errors** chart.
Copy file name to clipboardExpand all lines: content/en/s4r/9-custom-dashboard/1-custom-dashboard.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ As we already saved some useful log charts in a dashboard in the Log Observer ex
14
14
15
15
* Even if the log information is useful, it will need more information to have it make sense for our team so let's add a bit more information
16
16
* The first step is adding a description chart to the dashboard. Click on the {{% button style="gray" %}}New text note{{% /button %}} and replace the text in the note with below with the text then click the {{% button style="blue" %}}Save and close{{% /button %}} button and name the chart **Instructions**
17
+
17
18
{{% notice title=" information to use with text note" style="info" %}}
Copy file name to clipboardExpand all lines: content/en/s4r/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ weight: 1
4
4
hidden: true
5
5
---
6
6
7
-
In this workshop, we will be showing how Splunk Observability Cloud provides instant visibility of the user experience – from the perspective of the front-end application to its back-end services – showing off some of the most compelling product features and differentiators of the **Splunk Observability Cloud** Suite:
7
+
In this workshop, we will be showing how Splunk Observability Cloud provides instant visibility of the user experience – from the perspective of the front-end application to its back-end services – showing off some of the most compelling product features and differentiators of **Splunk Observability Cloud**:
0 commit comments