Improve configuration flow #357

Author: rcastley

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/8-routing-data/8-1-connector.md

@@ -11,10 +11,9 @@ In this exercise, you will configure the **Routing Connector** in the `gateway.y
 In OpenTelemetry configuration files, `connectors` have their own dedicated section, similar to receivers and processors.
 
 **Add the `routing` connector**:
-In the **Gateway terminal** window edit `gateway.yaml` and add the following below the `receivers:` section and above the `processors:` section:
+In the **Gateway terminal** window edit `gateway.yaml` and add the following below the `connectors:` section:
 
 ```yaml
-connectors:
   routing:
     default_pipelines: [traces/standard] # Default pipeline if no rule matches
     error_mode: ignore                   # Ignore errors in routing

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/8-routing-data/8-2-pipelines.md

@@ -6,6 +6,21 @@ weight: 2
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
+**Update the `traces` pipeline to use routing**:
+
+1. To enable `routing`, update the original `traces:` pipeline by using `routing` as the only exporter. This ensures all span data is sent through the routing connector for evaluation.
+2. Remove all processors and replace it with an empty array (`[]`). These are now defined in the `traces/standard` and `traces/security` pipelines.
+
+    ```yaml
+      pipelines:
+        traces:                           # Original traces pipeline
+          receivers: 
+          - otlp                          # OTLP Receiver
+          processors: []
+          exporters: 
+          - routing                       # Routing Connector
+    ```
+
 **Add both the `standard` and `security` traces pipelines**:
 
 1. **Add the Standard pipeline**: This pipeline processes all spans that do not match the routing rule.  
@@ -40,22 +55,6 @@ This also uses `routing` as its receiver. Add this below the Standard one:
           - file/traces/security      # File Exporter for spans matching rule
     ```
 
-**Update the `traces` pipeline to use routing**:
-
-1. To enable `routing`, update the original `traces:` pipeline by using `routing` as the only exporter.  
-This ensures all span data is sent through the routing connector for evaluation.
-2. Remove all processors and replace it with an empty array (`[]`). These are now defined in the `traces/standard` and `traces/security` pipelines.
-
-    ```yaml
-      pipelines:
-        traces:                           # Original traces pipeline
-          receivers: 
-          - otlp                          # OTLP Receiver
-          processors: []
-          exporters: 
-          - routing                       # Routing Connector
-    ```
-
 {{% /notice %}}
 
 Validate the agent configuration using **[otelbin.io](https://www.otelbin.io/)**. For reference, the `traces:` section of your pipelines will look similar to this: