diff --git a/content/en/s4r/1-workshop-goals/_index.md b/content/en/s4r/1-workshop-goals/_index.md index 6b5ecc9fc9..cce3dde7c2 100644 --- a/content/en/s4r/1-workshop-goals/_index.md +++ b/content/en/s4r/1-workshop-goals/_index.md @@ -4,6 +4,7 @@ linkTitle: 1. Workshop Overview weight: 1 archetype: chapter time: 2 minutes +description: Workshop Overview --- #### Introduction diff --git a/content/en/s4r/10-wrap-up/_index.md b/content/en/s4r/10-wrap-up/_index.md index a2e7336538..9df08c4f92 100644 --- a/content/en/s4r/10-wrap-up/_index.md +++ b/content/en/s4r/10-wrap-up/_index.md @@ -4,6 +4,7 @@ linkTitle: 10. Workshop Wrap-up weight: 10 archetype: chapter time: 10 minutes +description: Congratulations, you have completed the Splunk4Rookies - Observability Cloud Workshop. Today, you have become familiar with how to use Splunk Observability Cloud to monitor your applications and infrastructure. --- Congratulations, you have completed the **Splunk4Rookies - Observability Cloud Workshop**. Today, you have become familiar with how to use Splunk Observability Cloud to monitor your applications and infrastructure. diff --git a/content/en/s4r/2-opentelemetry/_index.md b/content/en/s4r/2-opentelemetry/_index.md index 9a59e10fc4..0821c650af 100644 --- a/content/en/s4r/2-opentelemetry/_index.md +++ b/content/en/s4r/2-opentelemetry/_index.md @@ -4,6 +4,7 @@ linkTitle: 2. OpenTelemetry weight: 2 archetype: chapter time: 2 minutes +description: Learn about OpenTelemetry and why you should care about it. --- ## OpenTelemetry diff --git a/content/en/s4r/3-quick-tour/1-homepage/_index.md b/content/en/s4r/3-quick-tour/1-homepage/_index.md index 188b825e86..5ac99f5a05 100644 --- a/content/en/s4r/3-quick-tour/1-homepage/_index.md +++ b/content/en/s4r/3-quick-tour/1-homepage/_index.md @@ -3,6 +3,7 @@ title: Getting Started linkTitle: 1. Getting Started weight: 1 time: 2 minutes +description: Learn how to get started with Splunk Observability Cloud. --- ### 1. Sign in to Splunk Observability Cloud diff --git a/content/en/s4r/3-quick-tour/2-rum-home/_index.md b/content/en/s4r/3-quick-tour/2-rum-home/_index.md index 9d011395c6..19179fc456 100644 --- a/content/en/s4r/3-quick-tour/2-rum-home/_index.md +++ b/content/en/s4r/3-quick-tour/2-rum-home/_index.md @@ -3,6 +3,7 @@ title: Real User Monitoring Overview linkTitle: 2. RUM Overview weight: 2 time: 5 minutes +description: Learn about Splunk RUM and how it can help you monitor the full user experience of every web and mobile session. --- Splunk RUM is the industry’s only end-to-end, **NoSample™** RUM solution - providing visibility into the full user experience of every web and mobile session to uniquely combine all front-end traces with back-end metrics, traces, and logs as they happen. IT Operations and Engineering teams can quickly scope, prioritize and isolate errors, measure how performance impacts real users and optimize end-user experiences by correlating performance metrics alongside video reconstructions of all user interactions. diff --git a/content/en/s4r/3-quick-tour/_index.md b/content/en/s4r/3-quick-tour/_index.md index cd0f48afbf..773a7216b0 100644 --- a/content/en/s4r/3-quick-tour/_index.md +++ b/content/en/s4r/3-quick-tour/_index.md @@ -3,6 +3,7 @@ title: UI - Quick Tour 🚌 linkTitle: 3. UI - Quick Tour weight: 3 archetype: chapter +description: A quick tour of the Splunk Observability Cloud UI. --- We are going to start with a short walkthrough of the various components of Splunk Observability Cloud. The aim of this is to get you familiar with the UI. diff --git a/content/en/s4r/4-online-boutique/_index.md b/content/en/s4r/4-online-boutique/_index.md index ff5f3d7823..21f349d1e7 100644 --- a/content/en/s4r/4-online-boutique/_index.md +++ b/content/en/s4r/4-online-boutique/_index.md @@ -3,6 +3,7 @@ title: Let's go shopping 💶 linkTitle: 4. Shopping at the Online Boutique weight: 4 time: 5 minutes +description: Interact with the Online Boutique web application to generate data for Splunk Observability Cloud. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/s4r/5-rum/_index.md b/content/en/s4r/5-rum/_index.md index bbccf232a3..2c3815df33 100644 --- a/content/en/s4r/5-rum/_index.md +++ b/content/en/s4r/5-rum/_index.md @@ -4,6 +4,7 @@ linkTitle: 5. Splunk RUM weight: 5 archetype: chapter time: 15 minutes +description: This section helps you understand how to use Splunk RUM to monitor the performance of your applications from the end user's perspective. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/s4r/6-apm/_index.md b/content/en/s4r/6-apm/_index.md index 1195c982dc..724bd1ca1e 100644 --- a/content/en/s4r/6-apm/_index.md +++ b/content/en/s4r/6-apm/_index.md @@ -4,6 +4,7 @@ linkTitle: 6. Splunk APM weight: 6 archetype: chapter time: 20 minutes +description: In this section, we will use APM to drill down and identify where the problem is. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/s4r/7-log-observer/_index.md b/content/en/s4r/7-log-observer/_index.md index 112dcc7dfd..d69d3331bf 100644 --- a/content/en/s4r/7-log-observer/_index.md +++ b/content/en/s4r/7-log-observer/_index.md @@ -4,6 +4,7 @@ linkTitle: 7. Splunk Log Observer weight: 7 archetype: chapter time: 20 minutes +description: In this section, we will use Log Observer to drill down and identify what the problem is. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/s4r/8-synthetics/_index.md b/content/en/s4r/8-synthetics/_index.md index 90d31b9bb2..d6d7ca5501 100644 --- a/content/en/s4r/8-synthetics/_index.md +++ b/content/en/s4r/8-synthetics/_index.md @@ -4,6 +4,7 @@ linkTitle: 8. Splunk Synthetics archetype: chapter weight: 8 time: 15 minutes +description: In this section, you will learn how to use Splunk Synthetics to monitor the performance and availability of your applications. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/s4r/9-custom-dashboard/_index.md b/content/en/s4r/9-custom-dashboard/_index.md index b6f9726196..612693cda9 100644 --- a/content/en/s4r/9-custom-dashboard/_index.md +++ b/content/en/s4r/9-custom-dashboard/_index.md @@ -4,6 +4,7 @@ linkTitle: 9. Service Health Dashboard weight: 9 archetype: chapter time: 15 minutes +description: In this section, you will learn how to build a custom Service Health Dashboard to monitor the health of your services. --- {{% notice icon="user" style="orange" title="Persona" %}} diff --git a/content/en/scenarios/optimize_monitoring/_index.md b/content/en/scenarios/optimize_monitoring/_index.md index 9346544a73..ceafc5f990 100644 --- a/content/en/scenarios/optimize_monitoring/_index.md +++ b/content/en/scenarios/optimize_monitoring/_index.md @@ -5,16 +5,19 @@ weight: 1 archetype: chapter authors: ["Tim Hard"] time: 3 minutes +description: This scenario is for ITOps teams managing a hybrid infrastructure that need to troubleshoot cloud-native performance issues, by correlating real-time metrics with logs to troubleshoot faster, improve MTTD/MTTR, and optimize costs. + + draft: false --- The elasticity of cloud architectures means that monitoring artifacts must scale elastically as well, breaking the paradigm of purpose-built monitoring assets. As a result, administrative overhead, visibility gaps, and tech debt skyrocket while MTTR slows. This typically happens for three reasons: -* **Complex and Inefficient Data Management**: Infrastructure data is scattered across multiple tools with inconsistent naming conventions, leading to fragmented views and poor metadata and labeling. Managing multiple agents and data flows adds to the complexity. +* **Complex and Inefficient Data Management**: Infrastructure data is scattered across multiple tools with inconsistent naming conventions, leading to fragmented views and poor metadata and labelling. Managing multiple agents and data flows adds to the complexity. * **Inadequate Monitoring and Troubleshooting Experience**: Slow data visualization and troubleshooting, cluttered with bespoke dashboards and manual correlations, are hindered further by the lack of monitoring tools for ephemeral technologies like Kubernetes and serverless functions. * **Operational and Scaling Challenges**: Manual onboarding, user management, and chargeback processes, along with the need for extensive data summarization, slow down operations and inflate administrative tasks, complicating data collection and scalability. -In order to address these challenges you need a way to: +To address these challenges you need a way to: * **Standardize Data Collection and Tags**: Centralized monitoring with a single, open-source agent to apply uniform naming standards and ensure metadata for visibility. Optimize data collection and use a monitoring-as-code approach for consistent collection and tagging. * **Reuse Content Across Teams**: Streamline new IT infrastructure onboarding and user management with templates and automation. Utilize out-of-the-box dashboards, alerts, and self-service tools to enable content reuse, ensuring uniform monitoring and reducing manual effort. @@ -23,14 +26,15 @@ In order to address these challenges you need a way to: In this workshop, we'll explore: -* How to standardize data collection and tags using **OpenTelemetry**. -* How to reuse content across teams. -* How to improve timeliness of alerts. -* How to correlate infrastructure metics and logs. +* How to standardize data collection and tags using **OpenTelemetry**. +* How to reuse content across teams. +* How to improve timelines of alerts. +* How to correlate infrastructure metrics and logs. {{% notice title="Tip" style="primary" icon="lightbulb" %}} The easiest way to navigate through this workshop is by using: * the left/right arrows (**<** | **>**) on the top right of this page * the left (◀️) and right (▶️) cursor keys on your keyboard - {{% /notice %}} \ No newline at end of file + {{% /notice %}} + \ No newline at end of file diff --git a/content/en/scenarios/self_service_observability/_index.md b/content/en/scenarios/self_service_observability/_index.md index 9bb44d8d7d..ce096a4d73 100644 --- a/content/en/scenarios/self_service_observability/_index.md +++ b/content/en/scenarios/self_service_observability/_index.md @@ -4,6 +4,9 @@ linkTitle: 5. Self-Service Observability weight: 5 archetype: chapter draft: true +description: This scenario helps platform engineering (or central tools) teams enable engineers with self-service observability tooling at scale, so developers and SREs can spend less time managing their toolchain and more time building and delivering cool software. + + --- TBD