Using title in code blocks instead of tabs.

rcastley · rcastley · commit a6b4852b2f0c · 2025-02-07T17:39:40.000Z
diff --git a/content/en/ninja-workshops/10-advanced-otel/1-agent/1-2-test-agent.md b/content/en/ninja-workshops/10-advanced-otel/1-agent/1-2-test-agent.md
@@ -52,20 +52,14 @@ This file will allow us to test how the OpenTelemetry Collector processes and se
 {{% /tab %}}
 {{% /tabs %}}
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 [WORKSHOP]
 ├── 1-agent         # Module directory
 │   └── agent.yaml  # OpenTelemetry Collector configuration file
 │   └── trace.json  # Sample trace data
 └── otelcol         # OpenTelemetry Collector binary
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-
 **Send a test span**: Run the following command to send a **span** to the agent:
 
 {{% tabs %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/1-agent/1-4-metadata/1-4-1-test-metadata.md b/content/en/ninja-workshops/10-advanced-otel/1-agent/1-4-metadata/1-4-1-test-metadata.md
@@ -39,10 +39,7 @@ Resource attributes:
 
 **Verify `agent.out`**: Validate the `agent.out` file contains the updated data:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
   [WORKSHOP]
   ├── 1-agent         # Module directory
   │   └── agent.out   # OTLP/Json output created by the File Exporter
@@ -51,9 +48,6 @@ Resource attributes:
   └── otelcol         # OpenTelemetry Collector binary
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-
 **Verify that metadata is added to spans in the new `agent.out` file**:
 
 1. Check for the existence of the`otelcol.service.mode` attribute in the `resourceSpans` section and that it has a value of `agent`.
diff --git a/content/en/ninja-workshops/10-advanced-otel/2-gateway/_index.md b/content/en/ninja-workshops/10-advanced-otel/2-gateway/_index.md
@@ -87,9 +87,7 @@ service:                          # Services configured for this Collector
 
 {{% /notice %}}
 
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 [WORKSHOP]
 ├── 1-agent             # Module directory
 ├── 2-gateway           # Module directory
@@ -98,5 +96,3 @@ service:                          # Services configured for this Collector
 │   └── trace.json      # Sample trace data
 └── otelcol             # OpenTelemetry Collector binary
 ```
-
-{{% /tab %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-1-create-loggen.md b/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-1-create-loggen.md
@@ -153,10 +153,7 @@ while ($true) {
 {{% /tab %}}
 {{% /tabs %}}
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -168,9 +165,6 @@ WORKSHOP
 └── otelcol                 # OpenTelemetry Collector binary
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-
 For **macOS/Linux** make sure the script is executable:
 
 ```bash
diff --git a/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-2-start-loggen.md b/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-2-start-loggen.md
@@ -8,11 +8,11 @@ weight: 2
 
 Start the appropriate script for your system. The script will begin writing lines to a file named `quotes.log`:
 
-```sh
+```sh { title="Log Generator" }
 ./log-gen.sh
 ```
 
-```text
+```text { title="Log Generator Output" }
 Writing logs to quotes.log. Press Ctrl+C to stop.
 ```
 
diff --git a/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-4-test-filelog.md b/content/en/ninja-workshops/10-advanced-otel/3-filelog/3-4-test-filelog.md
@@ -71,10 +71,7 @@ Flags: 0
 
 At this point, your directory structure will appear as follows:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -89,9 +86,6 @@ WORKSHOP
 └── otelcol                 # OpenTelemetry Collector binary
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-
 **Examine a log line in `gateway-log.out`**: Compare a log line with the snippet below. It is a preview showing the beginning and a single log line; your actual output will contain many, many more:
 
 {{% tabs %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/3-filelog/_index.md b/content/en/ninja-workshops/10-advanced-otel/3-filelog/_index.md
@@ -21,10 +21,7 @@ For this part of the workshop, there is script that will generate log lines in a
 
 Your updated directory structure will now look like this:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -35,6 +32,4 @@ WORKSHOP
 └── otelcol                 # OpenTelemetry binary
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
 {{% /notice %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/4-building-resilience/4-2-test-environment.md b/content/en/ninja-workshops/10-advanced-otel/4-building-resilience/4-2-test-environment.md
@@ -10,19 +10,19 @@ Next, we will configure our environment to be ready for testing the **File Stora
 
 **Start the Gateway**: In the **Gateway** terminal window navigate to the `[WORKSHOP]/4-resilience` directory and run:
 
-```sh
+```sh { title="Gateway" }
 ../otelbin --config=gateway.yaml
 ```
 
 **Start the Agent**: In the **Agent** terminal window navigate to the `[WORKSHOP]/4-resilience` directory and run:
 
-```sh
+```sh { title="Agent" }
 ../otelbin --config=agent.yaml
 ```
 
 **Send a test trace**: In the **Test** terminal window navigate to the `[WORKSHOP]/4-resilience` directory and run:
 
-```sh
+```sh { title="cURL command" }
 curl -X POST -i http://localhost:4318/v1/traces -H "Content-Type: application/json" -d "@trace.json"
 ```
 
diff --git a/content/en/ninja-workshops/10-advanced-otel/4-building-resilience/_index.md b/content/en/ninja-workshops/10-advanced-otel/4-building-resilience/_index.md
@@ -26,10 +26,7 @@ For logs, there are plans to implement a more enterprise-ready solution in one o
 
 Your updated directory structure will now look like this:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -42,7 +39,4 @@ WORKSHOP
 └── otelcol
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-
 {{% /notice %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/5-dropping-spans/5-2-test-filter.md b/content/en/ninja-workshops/10-advanced-otel/5-dropping-spans/5-2-test-filter.md
@@ -14,19 +14,11 @@ To test your configuration, you'll need to generate some trace data that include
 2. Copy and paste the following JSON into the `health.json` file.
 3. Note the span name is set to `{"name":"healthz"}` in the json.
 
-{{% tabs %}}
-{{% tab title="health.json" %}}
-
-```json
+```json { title="health.json" }
 {"resourceSpans":[{"resource":{"attributes":[{"key":"service.name","value":{"stringValue":"frontend"}}]},"scopeSpans":[{"scope":{"name":"healthz","version":"1.0.0","attributes":[{"key":"my.scope.attribute","value":{"stringValue":"some scope attribute"}}]},"spans":[{"traceId":"5B8EFFF798038103D269B633813FC60C","spanId":"EEE19B7EC3C1B174","parentSpanId":"EEE19B7EC3C1B173","name":"/_healthz","startTimeUnixNano":"1544712660000000000","endTimeUnixNano":"1544712661000000000","kind":2,"attributes":[]}]}]}]}
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -42,30 +34,27 @@ WORKSHOP
 └── otelcol
 ```
 
-{{% /tabs %}}
-{{% /tab %}}
-
 **Start the Gateway**: In the **Gateway** terminal window navigate to the `[WORKSHOP]/5-dropping-spans` directory and run:
 
-```sh
+```sh { title="Gateway" }
 ../otelbin --config=gateway.yaml
 ```
 
 **Start the Agent**: In the **Agent** terminal window navigate to the `[WORKSHOP]/5-dropping-spans` directory and run:
 
-```sh
+```sh { title="Agent" }
 ../otelbin --config=agent.yaml
 ```
 
 **Send the new `health.json` payload:** In the **Test** terminal window navigate to the `[WORKSHOP]/5-dropping-spans` directory and run the `curl` command below. (**Windows use `curl.exe`**).
   
-```sh
+```sh { title="cURL command" }
 curl -X POST -i http://localhost:4318/v1/traces -H "Content-Type: application/json" -d "@health.json"
 ```
 
 **Verify Agent Debug output shows the `healthz` span**: Confirm that the span `span` payload is sent, Check the agent’s debug output to see the span data like the snippet below:
 
-```text
+```text { title="Debug Output" }
 <snip>
 Span #0
     Trace ID       : 5b8efff798038103d269b633813fc60c
diff --git a/content/en/ninja-workshops/10-advanced-otel/5-dropping-spans/_index.md b/content/en/ninja-workshops/10-advanced-otel/5-dropping-spans/_index.md
@@ -18,10 +18,7 @@ Specifically, we will drop traces based on the span name, which is commonly used
 
 Your updated directory structure will now look like this:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -36,8 +33,6 @@ WORKSHOP
 └── otelcol
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
 {{% /notice %}}
 
 Next, we will configure the **filter processor** and the respective pipelines.
diff --git a/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/6-2-test-delete-tag.md b/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/6-2-test-delete-tag.md
@@ -10,13 +10,13 @@ In this exercise, we will **delete** the `user.account_password`, **update** the
 
 **Start the Gateway**: In the **Gateway** terminal window navigate to the `[WORKSHOP]/6-sensitive-data` directory and run:
 
-```sh
+```sh { title="Gateway" }
 ../otelbin --config=gateway.yaml
 ```
 
 **Start the Agent**: In the **Agent** terminal window navigate to the `[WORKSHOP]/6-sensitive-data` directory and run:
 
-```sh
+```sh { title="Agent" }
 ../otelbin --config=agent.yaml
 ```
 
diff --git a/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/6-3-test-redaction.md b/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/6-3-test-redaction.md
@@ -27,23 +27,23 @@ This is achieved using the `redaction` processor you added earlier, where we def
 
 In this exercise, we will **redact** the `user.visa` & `user.mastercard` **values** in the span data before it is exported by the **Agent**.
 {{% notice title="Exercise" style="green" icon="running" %}}
-Delete the `*.out` files and clear the screen. 
+
+**Prepare the terminals**: Delete the `*.out` files and clear the screen.
 
 **Enable the `redaction/redact` processor**: Edit `agent.yaml` and remove the `#` we inserted in the previous exercise.
 
 **Start the Gateway**: In the **Gateway** terminal window navigate to the `[WORKSHOP]/6-sensitive-data` directory and run:
 
-```sh
+```sh { title="Gateway" }
 ../otelbin --config=gateway.yaml
 ```
 
 **Start the Agent**: In the **Agent** terminal window navigate to the `[WORKSHOP]/6-sensitive-data` directory and run:
 
-```sh
+```sh { title="Agent" }
 ../otelbin --config=agent.yaml
 ```
 
-
 **Send a span**: Run the `curl` command and in the **Test** terminal window to send `trace.json`.
 
 **Check the debug output**: For both the **Agent** and **Gateway** confirm the values for `user.visa` & `user.mastercard` have been updated. Notice `user.amex` attribute value was NOT redacted because a matching regex pattern was not added to `blocked_values`
diff --git a/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/_index.md b/content/en/ninja-workshops/10-advanced-otel/6-sensitive-data/_index.md
@@ -21,10 +21,7 @@ We'll walk through configuring key processors in the OpenTelemetry Collector, in
 
 Your updated directory structure will now look like this:
 
-{{% tabs %}}
-{{% tab title="Updated Directory Structure" %}}
-
-```text
+```text { title="Updated Directory Structure" }
 WORKSHOP
 ├── 1-agent
 ├── 2-gateway
@@ -41,6 +38,4 @@ WORKSHOP
 └── otelcol
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
 {{% /notice %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/7-transform-data/7-1-configuration.md b/content/en/ninja-workshops/10-advanced-otel/7-transform-data/7-1-configuration.md
@@ -6,7 +6,8 @@ weight: 1
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-**Configure the `transform` processor** and name it `/logs`: By using the `-context: resource` key we are targeting the **resourceLog** attributes of logs.  
+**Configure the `transform` processor** and name it `/logs`: By using the `-context: resource` key we are targeting the `resourceLog` attributes of logs.
+
 This configuration ensures that only the relevant resource attributes (`com.splunk.sourcetype`, `host.name`, `otelcol.service.mode`) are retained, improving log efficiency and reducing unnecessary metadata.
 
 ```yaml
@@ -17,7 +18,8 @@ This configuration ensures that only the relevant resource attributes (`com.splu
           - keep_keys(attributes, ["com.splunk.sourcetype", "host.name", "otelcol.service.mode"])
 ```
 
-**Adding a Context Block for Log Severity Mapping**: To properly set the `severity_text` and `severity_number` fields of a log record, we add another log `context` block within `log_statements`.  
+**Adding a Context Block for Log Severity Mapping**: To properly set the `severity_text` and `severity_number` fields of a log record, we add another log `context` block within `log_statements`.
+
 This configuration extracts the `level` value from the log body, maps it to `severity_text`, and assigns the appropriate `severity_number`:
 
 ```yaml
@@ -62,8 +64,8 @@ This method of mapping all JSON fields to top-level attributes should only be us
       - memory_limiter           # Memory Limiter Processor
       - resourcedetection        # Adds system attributes to the data
       - resource/add_mode        # Adds collector mode metadata
-      - transform/logs           # Transform Processor used to update log lines
-      - batch                    # Batch Processor, groups data before send   
+      - transform/logs           # Transform Processor to update log lines
+      - batch                    # Batch Processor, groups data before send
 ```
 
 {{% /notice %}}
diff --git a/content/en/ninja-workshops/10-advanced-otel/7-transform-data/7-2-setup.md b/content/en/ninja-workshops/10-advanced-otel/7-transform-data/7-2-setup.md
@@ -8,25 +8,25 @@ weight: 2
 
 **Start the Log Generator**: In the **Test** terminal window, navigate to the `[WORKSHOP]/7-transform-data` directory and start the appropriate `log-gen` script for your system. We want to work with structured JSON logs, so add the `-json` flag.
 
-```sh
+```sh { title="Log Generator" }
 ./log-gen.sh -json
 ```
 
 The script will begin writing lines to a file named `./quotes.log`, while displaying a single line of output in the console.
 
-```txt
+```txt { title="Log Generator Output" }
 Writing logs to quotes.log. Press Ctrl+C to stop.
 ```
 
 **Start the Gateway**: In the **Gateway** terminal window navigate to the `[WORKSHOP]/7-transform-data` directory and run:
 
-```sh
+```sh { title="Gateway" }
 ../otelbin --config=gateway.yaml
 ```
 
 **Start the Agent**: In the **Agent** terminal window navigate to the `[WORKSHOP]/7-transform-data` directory and run:
 
-```sh
+```sh { title="Agent" }
 ../otelbin --config=agent.yaml
 ```
 
diff --git a/content/en/ninja-workshops/10-advanced-otel/7-transform-data/_index copy.md b/content/en/ninja-workshops/10-advanced-otel/7-transform-data/_index copy.md
diff --git a/content/en/ninja-workshops/10-advanced-otel/7-transform-data/_index.md b/content/en/ninja-workshops/10-advanced-otel/7-transform-data/_index.md
diff --git a/content/en/ninja-workshops/10-advanced-otel/8-routing-data/_index.md b/content/en/ninja-workshops/10-advanced-otel/8-routing-data/_index.md
