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

Author: geoffhigginbottom

content/en/s4r/3-quick-tour/3-apm-home/_index.md

@@ -8,7 +8,7 @@ weight: 3
 
 Splunk APM provides a **NoSample™** end-to-end visibility of every service and its dependency to solve problems quicker across monoliths and microservices. Teams can immediately detect problems from new deployments, confidently troubleshoot by scoping and isolating the source of an issue, and optimize service performance by understanding how back-end services impact end users and business workflows.
 
-**Real-time monitoring and alerting:** Splunk provides a 10-second resolution on metrics to detect and alert on issues when they happen.  
+**Real-time monitoring and alerting:** Splunk provides out-of-the-box service dashboards and automatically detects and alerts on RED metrics (rate, error and duration) when there is a sudden change.
 **Dynamic telemetry maps:** Easily visualize service performance in modern production environments in real-time. End-to-end visibility of service performance from infrastructure, applications, end users, and all dependencies helps quickly scope new issues and troubleshoot more effectively.  
 **Intelligent tagging and analysis:** View all tags from your business, infrastructure and applications in one place to easily compare new trends in latency or errors to their specific tag values.  
 **AI-directed troubleshooting identifies the most impactful issues:** Instead of manually digging through individual dashboards, isolate problems more efficiently. Automatically identify anomalies and the sources of errors that impact services and customers the most.  

content/en/s4r/3-quick-tour/4-log-observer-home/1-log-observer-home.md

@@ -18,8 +18,11 @@ Click **Log Observer** in the main menu, the Log Observer Home Page is made up o
 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.
 
 {{% /notice %}}
-{{% notice title="Tip" style="primary"  icon="lightbulb" %}}
-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.
+
+{{% notice title="Tip" style="primary" icon="lightbulb" %}}
+
+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.
+
 {{% /notice %}}
 
 Let's run a little search exercise:
@@ -37,9 +40,9 @@ Let's run a little search exercise:
 * Let's find all the orders that have been shipped. Click on **Clear All** in the filter bar to remove the previous filter.
 * In the **Fields** Pane type `severity` in the search box.
   ![severity](../images/find-severity.png?width=15vw&classes=left)
-* 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.
-* 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.
-* Click on the {{% button style="gray"  %}}**Add Filter**{{% /button %}} button in the filter bar.
+* 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.
+* 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.
+* Click on the {{% button style="grey" %}}**Add Filter**{{% /button %}} button in the filter bar.
 * This time, just type `order:` in the **Enter Keyword...** box and press enter.
 * You should now have a list of orders sold for the last 15 minutes.
 

content/en/s4r/7-log-observer/2-log-entry.md

@@ -22,7 +22,7 @@ Before we look at a specific log line, let's quickly recap what we have done so
 **Based on the message, what would you tell the development teams to do to resolve the issue?**
 {{% /tab %}}
 {{% tab title="Answer" %}}
-**Either fix the issue in `v350.10` or rollback to `v350.9`**
+**Either fix the issue in `v350.10` or rollback to `v350.9`.**
 {{% /tab %}}
 {{< /tabs >}}
 

content/en/s4r/7-log-observer/3-log-timeline-chart.md

@@ -25,7 +25,7 @@ First, we will reduce the amount of information to just the columns we are inter
   ![log timeline](../images/log-timeline.png?classes=left&width=25vw)
 * Click {{% button style="blue" %}}Select Dashboard{{% /button %}} and then click {{% button style="blue" %}}New Dashboard{{% /button %}} in the Dashboard Selection dialog box.
 * In the **New dashboard** dialog box, enter a name for the new dashboard (no need to enter a description). Use the following format: `Initials - Service Health Dashboard` and click {{% button style="blue" %}}Save{{% /button %}}
-* Ensure the new dashboard is highlighted in the list **[1]** and click {{% button style="blue" %}}OK{{% /button %}} **[2]**
+* Ensure the new dashboard is highlighted in the list (**1**) and click {{% button style="blue" %}}OK{{% /button %}} (**2**).
   ![Save dashboard](../images/dashboard-save.png)
 * Click the {{% button %}}Save{{% /button %}} button.
 

content/en/s4r/7-log-observer/4-log-view-chart.md

@@ -17,18 +17,18 @@ As with the previous Log Timeline chart, we will add a version of this chart to
 * Ensure **Log View** is selected as the **Chart Type**.
   ![log view](../images/log-view.png?classes=left&width=30vw)
 * Enter a **Chart name**. Use the following format: `Initials - Log View Chart`
-* This time Click {{% button style="blue" %}}Select Dashboard{{% /button %}} and search for the Dashboard you created in the previous exercise (you can start by typing your initials in the search box **[1]**).
+* This time Click {{% button style="blue" %}}Select Dashboard{{% /button %}} and search for the Dashboard you created in the previous exercise. You can start by typing your initials in the search box (**1**).
   ![search dashboard](../images/search-dashboard.png)
-* Click on your dashboard name to highlight it **[2]** and click {{% button style="blue" %}}OK{{% /button %}} **[3]**.
+* Click on your dashboard name to highlight it (**2**) and click {{% button style="blue" %}}OK{{% /button %}} (**3**).
 * This will return you to the create chart dialog. To see your dashboard click {{% button style="blue" %}}Save and go to dashboard{{% /button %}}.
 * The result should be similar to the dashboard below:
   ![Custom Dashboard](../images/log-observer-custom-dashboard.png)
 * As the last step in this exercise, let us add your dashboard to your workshop team page, this will make it easy to find later in the workshop.
-* At the top of the page, click on the ***...*** behind the name of your dashboard **[1]**.
-* Select **Link to teams** from the drop-down **[2]**.
+* At the top of the page, click on the ***...*** behind the name of your dashboard (**1**).
+* Select **Link to teams** from the drop-down (**2**).
 * In the following **Link to teams** dialog box, find the Workshop team that your instructor will have provided for you.
   ![linking](../images/linking.png)
 
 {{% /notice %}}
 
-In the next session, we will look at Splunk Synthetics to see how we can automate the testing of web-based applications.
+In the next session, we will look at Splunk Synthetics and see how we can automate the testing of web-based applications.