Updated directory trees #357

Author: rcastley

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/1-agent/1-1-validation.md

@@ -17,7 +17,8 @@ Here’s how to validate your configuration:
     > cat agent.yaml | pbcopy
     > ```
 
-2. At the top of the page, make sure **Splunk OpenTelemetry Collector** is selected as the validation target.
+2. At the top of the page, make sure **Splunk OpenTelemetry Collector** is selected as the validation target. If you **don't** select this option, then you will see warnings in the UI stating `Receiver "hostmetrics" is unused. (Line 8)`.
+
 3. Once validated, refer to the image representation below to confirm your pipelines are set up correctly.
 
 In most cases, we’ll display only the **key pipeline**. However, if all three pipelines (Traces, Metrics, and Logs) share the same structure, we’ll note this instead of showing each one individually.

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/1-agent/1-3-fileexporter/1-test-fileexporter.md

@@ -34,10 +34,9 @@ weight: 1
 **Verify that the `agent.out` file is written**: Check that a file named `agent.out` is written in the current directory.
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 1-agent
-    └── agent.out   # OTLP/Json output created by the File Exporter
-    └── agent.yaml
+.
+├── agent.out    # OTLP/Json output created by the File Exporter
+└── agent.yaml
 ```
 
 **Verify the span format**:

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/1-agent/1-3-fileexporter/_index.md

@@ -1,7 +1,7 @@
 ---
 title: 1.3 File Exporter
 linkTitle: 1.3 File Exporter
-weight: 1
+weight: 2
 ---
 
 To capture more than just debug output on the screen, we also want to generate output during the export phase of the pipeline. For this, we'll add a **File Exporter** to write OTLP data to files for comparison.

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/2-gateway/_index.md

@@ -104,10 +104,9 @@ service:                          # Service configuration
 ```
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 2-gateway
-    └── agent.yaml
-    └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 {{% /notice %}}

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/3-filelog/3-2-test-filelog.md

@@ -32,15 +32,14 @@ LogRecord #1
 At this point, your directory structure will appear as follows:
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 3-filelog
-    ├── agent.out
-    ├── agent.yaml
-    ├── gateway-logs.out    # Output from the logs pipeline
-    ├── gateway-metrics.out # Output from the metrics pipeline
-    ├── gateway-traces.out  # Output from the traces pipeline
-    ├── gateway.yaml
-    └── quotes.log          # File containing Random log lines
+.
+├── agent.out
+├── agent.yaml
+├── gateway-logs.out     # Output from the logs pipeline
+├── gateway-metrics.out  # Output from the metrics pipeline
+├── gateway-traces.out   # Output from the traces pipeline
+├── gateway.yaml
+└── quotes.log           # File containing Random log lines
 ```
 
 **Examine a log line**: In `gateway-logs.out` compare a log line with the snippet below. Verify that the log entry includes the same attributes as we have seen in metrics and traces data previously:

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/3-filelog/_index.md

@@ -38,10 +38,9 @@ The **FileLog receiver** in the `agent` will read these log lines and send them
 > **Change _ALL_ terminal windows to the `[WORKSHOP]/3-filelog` directory.**
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 3-filelog
-    ├── agent.yaml
-    └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 Start the `loadgen` and this will begin writing lines to a file named `quotes.log`:

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/4-building-resilience/_index.md

@@ -28,10 +28,9 @@ For logs, there are plans to implement a more enterprise-ready solution in one o
 Your updated directory structure will now look like this:
 
 ```text { title="Updated Directory Structure" }
-WORKSHOP
-└── 4-resilience
-│   ├── agent.yaml
-│   └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 {{% /notice %}}

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/5-dropping-spans/_index.md

@@ -20,10 +20,9 @@ Specifically, we will drop traces based on the span name, which is commonly used
 Your updated directory structure will now look like this:
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 5-dropping-spans
-    ├── agent.yaml
-    └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 {{% /notice %}}

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/6-sensitive-data/_index.md

@@ -23,10 +23,9 @@ We'll walk through configuring key processors in the OpenTelemetry Collector, in
 Your updated directory structure will now look like this:
 
 ```text { title="Updated Directory Structure" }
-[WORKSHOP]
-└── 6-sensitive-data
-    ├── agent.yaml
-    └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 {{% /notice %}}

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/7-transform-data/_index.md

@@ -36,10 +36,9 @@ Logs often contain structured data encoded as JSON within the log body. Extracti
 Your updated directory structure will now look like this:
 
 ```text { title="Updated Directory Structure" }
-WORKSHOP
-└── 7-transform-data
-    ├── agent.yaml
-    └── gateway.yaml
+.
+├── agent.yaml
+└── gateway.yaml
 ```
 
 {{% /notice %}}