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
Copy file name to clipboardExpand all lines: content/en/s4r/3-quick-tour/4-log-observer-home/1-log-observer-home.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,11 @@ Click **Log Observer** in the main menu, the Log Observer Home Page is made up o
18
18
Generally, in Splunk, an "index" refers to a designated place where your data is stored. It's like a folder or container for your data. Data within a Splunk index is organized and structured in a way that makes it easy to search and analyze. Different indexes can be created to store specific types of data. For example, you might have one index for web server logs, another for application logs, and so on.
If you have used Splunk Enterprise or Splunk Cloud before, you are probably used to starting investigations with logs. As you will see in the following exercise, you can do that with Splunk Observability Cloud as well. This workshop however, will use all the **OpenTelemetry** signals for investigations.
If you have used Splunk Enterprise or Splunk Cloud before, you are probably used to starting investigations with logs. As you will see in the following exercise, you can do that with Splunk Observability Cloud as well. This workshop, however, will use all the **OpenTelemetry** signals for investigations.
25
+
23
26
{{% /notice %}}
24
27
25
28
Let's run a little search exercise:
@@ -37,9 +40,9 @@ Let's run a little search exercise:
37
40
* Let's find all the orders that have been shipped. Click on **Clear All** in the filter bar to remove the previous filter.
38
41
* In the **Fields** Pane type `severity` in the search box.
* You may need to scroll down the page if you still have the onboarding content displayed at the top in order to see the **Exclude all logs with this fields** button in the next step.
41
-
* Make sure you click the {{% button style="gray" %}}**Exclude all logs with this fields**{{% /button %}} as the order log line does not have a severity assigned.
42
-
* Click on the {{% button style="gray" %}}**Add Filter**{{% /button %}} button in the filter bar.
43
+
* You may need to scroll down the page if you still have the onboarding content displayed at the top to see the **Exclude all logs with this fields** button in the next step.
44
+
* Make sure you click the {{% button style="grey" %}}**Exclude all logs with this fields**{{% /button %}} as the order log line does not have a severity assigned.
45
+
* Click on the {{% button style="grey" %}}**Add Filter**{{% /button %}} button in the filter bar.
43
46
* This time, just type `order:` in the **Enter Keyword...** box and press enter.
44
47
* You should now have a list of orders sold for the last 15 minutes.
0 commit comments