updates

Author: greatestusername

content/en/splunk4rookies/financial-services-observability-cloud/1-workshop-goals/_index.md

@@ -8,7 +8,7 @@ description: Workshop Overview
 ---
 
 **Introduction**  
-The goal of this workshop is to give you hands-on experience troubleshooting an issue using Splunk Observability Cloud to identify its root cause. We’ve provided a fully instrumented microservices-based application that actually mimic a payment workflow that is running on Kubernetes, which sends metrics, traces, and logs to Splunk Observability Cloud for real-time analysis.
+The goal of this workshop is to give you hands-on experience troubleshooting an issue using Splunk Observability Cloud to identify its root cause. We’ve provided a fully instrumented microservices-based application that actually mimic a wire transfer workflow that is running on Kubernetes, which sends metrics, traces, and logs to Splunk Observability Cloud for real-time analysis.
 
 **Who Should Attend?**  
 This workshop is ideal for anyone looking to gain practical knowledge of Splunk Observability. It's designed for individuals with little or no prior experience with the platform.

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/2-apm-home/1-apm-home.md

@@ -29,7 +29,7 @@ To easily differentiate between multiple applications, Splunk uses **environment
 **What can you conclude from the *Top Services by Error Rate* chart?**
 {{% /tab %}}
 {{% tab title="Answer" %}}
-**The *paymentservice* has a high error rate**
+**The *wire-transfer-service* has a high error rate**
 {{% /tab %}}
 {{< /tabs >}}
 <!--

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/2-apm-home/_index.md

@@ -7,12 +7,18 @@ time: 5 minutes
 
 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 out-of-the-box service dashboards and automatically detects and alerts on RED metrics (rate, error and duration) when there is a sudden change.
+**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.  
+
 **Complete distributed tracing analyses every transaction:** Identify problems in your cloud-native environment more effectively. Splunk distributed tracing visualizes and correlates every transaction from the back-end and front-end in context with your infrastructure, business workflows and applications.  
+
 **Full stack correlation:** Within Splunk Observability, APM links traces, metrics, logs and profiling together to easily understand the performance of every component and its dependency across your stack.  
+
 **Monitor database query performance:** Easily identify how slow and high execution queries from SQL and NoSQL databases impact your services, endpoints and business workflows — no instrumentation required.  
 
 ![Architecture Overview](./images/arch-overview.png)

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/3-log-observer-home/1-log-observer-home.md

@@ -38,15 +38,15 @@ Let's run a little search exercise:
   ![logo search](../images/log-filter-bar.png?width=920px)
 
 * Click on one of the log entries in the Logs table to validate that the entry contains `cardType: "visa"`.
-* Let's find all the orders that have been shipped. Click on **Clear All** in the filter bar to remove the previous filter.
+* Let's find all the wire transfer orders that have been compelted. Click on {{% button style="gray" %}}Clear All{{% /button %}} in the filter bar to remove the previous filter.
 * Click again on {{% button style="gray" %}}Add Filter{{% /button %}} in the filter bar, then select **Keyword**. Next just type `order` in the **Enter Keyword...** box and press enter.
 * Click {{% button style="blue" %}}Run search{{% /button %}}
-* You should now only have log lines that contain the word `order`. There are still a lot of log lines, so let's filter some more.
+* You should now only have log lines that contain the word `order`. There are still a lot of log lines -- some of which may not be our service -- so let's filter some more.
 * Add another filter, this time select the **Fields** box, then type `severity` in the **Find a field ...** search box and select it.
   ![severity](../images/find-severity.png?width=15vw&classes=left)
 * Under **Top values** click on **error**, then click on **=** to add it to the filter.
 * Click {{% button style="blue" %}}Run search{{% /button %}}
-* You should now have a list of orders that failed to complete for the last 15 minutes.
+* You should now have a list of wire transfer orders that failed to complete for the last 15 minutes.
 
 {{% /notice %}}
 

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/3-log-observer-home/_index.md

@@ -8,7 +8,9 @@ time: 5 minutes
 Log Observer Connect allows you to seamlessly bring in the same log data from your Splunk Platform into an intuitive and **no-code** interface designed to help you find and fix problems quickly. You can easily perform log-based analysis and seamlessly correlate your logs with Splunk Infrastructure Monitoring’s real-time metrics and Splunk APM traces in one place.
 
 **End-to-end visibility:** By combining the powerful logging capabilities of Splunk Platform with Splunk Observability Cloud’s traces and real-time metrics for deeper insights and more context of your hybrid environment.  
+
 **Perform quick and easy log-based investigations:** By reusing logs that are already ingested in Splunk Cloud Platform or Enterprise in a simplified and intuitive interface (no need to know SPL!) with customizable and out-of-the-box dashboards  
+
 **Achieve higher economies of scale and operational efficiency:** By centralizing log management across teams, breaking down data and team silos, and getting better overall support
 
 ![Logo graph](./images/logo-image-loop.png)

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/4-infrastructure-home/_index.md

@@ -8,11 +8,17 @@ time: 5 minutes
 Splunk Infrastructure Monitoring (IM) is a market-leading monitoring and observability service for hybrid cloud environments. Built on a patented streaming architecture, it provides a **real-time** solution for engineering teams to visualize and analyze performance across infrastructure, services, and applications in a fraction of the time and with greater accuracy than traditional solutions.
 
 **OpenTelemetry standardization:** Gives you full control over your data — freeing you from vendor lock-in and implementing proprietary agents.  
+
 **Splunk’s OTel Collector:** Seamless installation and dynamic configuration, auto-discovers your entire stack in seconds for visibility across clouds, services, and systems.  
+
 **300+ Easy-to-use OOTB content:** Pre-built navigators and dashboards, deliver immediate visualizations of your entire environment so that you can interact with all your data in real time.  
+
 **Kubernetes navigator:** Provides an instant, comprehensive out-of-the-box hierarchical view of nodes, pods, and containers. Ramp up even the most novice Kubernetes user with easy-to-understand interactive cluster maps.  
+
 **AutoDetect alerts and detectors:** Automatically identify the most important metrics, out-of-the-box, to create alert conditions for detectors that accurately alert from the moment telemetry data is ingested and use real-time alerting capabilities for important notifications in seconds.  
+
 **Log views in dashboards:** Combine log messages and real-time metrics on one page with common filters and time controls for faster in-context troubleshooting.  
+
 **Metrics pipeline management:** Control metrics volume at the point of ingest without re-instrumentation with a set of aggregation and data-dropping rules to store and analyze only the needed data. Reduce metrics volume and optimize observability spend.  
 
-![Infrastructure Overview](../images/infrastructure-overview.png)
+![Infrastructure Overview](./images/infrastructure-over.png)

content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/4-infrastructure-home/images/infrastructure-overview.png renamed to content/en/splunk4rookies/financial-services-observability-cloud/3-quick-tour/4-infrastructure-home/images/infrastructure-over.png

@@ -3,11 +3,11 @@ title: 1. APM Explore
 weight: 1
 ---
 
-The APM Service Map displays the dependencies and connections among your instrumented and inferred services in APM. The map is dynamically generated based on your selections in the time range, environment, workflow, service, and tag filters.
+When you click into the APM section of Splunk Observability Cloud you are greated with an overview of your APM data including top services by error rates, and R.E.D. metrics for services and workflows.
 
-When we clicked on the APM link in the RUM waterfall, filters were automatically added to the service map view to show the services that were involved in that **WorkFlow Name** (`frontend:/cart/checkout`).
+The APM Service Map displays the dependencies and connections among your instrumented and inferred services in APM. The map is dynamically generated based on your selections in the time range, environment, workflow, service, and tag filters.
 
-You can see the services involved in the workflow in the **Service Map**. In the side pane, under **Business Workflow**, charts for the selected workflow are displayed. The **Service Map** and **Business Workflow** charts are synchronized. When you select a service in the **Service Map**, the charts in the **Business Workflow** pane are updated to show metrics for the selected service.
+You can see the services involved in any of your APM user workflows by clicking into the **Service Map**. When you select a service in the **Service Map**, the charts in the **Business Workflow** sidepane are updated to show metrics for the selected service. The **Service Map** and any indicators are syncronized with the time picker and chart data displayed. 
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
@@ -21,7 +21,7 @@ Splunk APM also provides built-in **Service Centric Views** to help you see prob
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* In the right hand pane, click on **paymentservice** in blue.
+* In the right hand pane, click on **wire-transfer-service** in blue.
 
 {{% /notice %}}
 

content/en/splunk4rookies/financial-services-observability-cloud/4-apm/1-apm-explore.md

@@ -12,8 +12,7 @@ As a service owners you can use the service view in Splunk APM to get a complete
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* Check the **Time** box, you can see that the dashboards only show data relevant to the time it took for the APM trace we previosuly selected to complete (note that the charts are static).
-* In the **Time** box change the timeframe to **-1h**.
+* In the **Time** box change the timeframe to **-1h**. Note how the charts update.
 * These charts are very useful to quickly identify performance issues. You can use this dashboard to keep an eye on the health of your service.
 * Scroll down the page and expand **Infrastructure Metrics**. Here you will see the metrics for the Host and Pod.
 * **Runtime Metrics** are not available as profiling data is not available for services written in Node.js.

content/en/splunk4rookies/financial-services-observability-cloud/4-apm/2-apm-service-view.md

@@ -24,6 +24,8 @@ It is also possible to configure which tag metrics are displayed in the cards. I
 
 Also ensure that the **Show tags with no values** toggle is unchecked.
 
+Scroll through the cards and get familiar with the tags provided by the wire-transfer-service's telemetry.
+
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 {{< tabs >}}
@@ -37,4 +39,4 @@ Also ensure that the **Show tags with no values** toggle is unchecked.
 
 {{% /notice %}}
 
-Now that we have identified the version of the **wire-transfer-service** that is causing the issue, let's see if we can find out more information about the error. Click on **← Tag Spotlight** at the top of the page to get back to the Service Map.
+Now that we have identified the version of the **wire-transfer-service** that is causing the issue, let's see if we can find out more information about the error. Press the back button on your browser to get back to the Service Map.