last changes to routing

Author: hagen-p

content/en/ninja-workshops/10-advanced-otel/80-routing/8-1-routing-test.md

@@ -104,20 +104,23 @@ Make sure the are **NO** `*.out` files in the `[WORKSHOP]/8-routing` folder.
 
 - **Send a Regular Span**:  
 Find your `Test` terminal window and navigate to the `[WORKSHOP]/8-routing` folder. From there, send a regular span using the `trace.json` file to confirm that communication is functioning as expected.  
-Both the `agent` and `gateway` should display debug information, including the span you just sent. Additionally, the gateway should generate a new `./gateway-traces-default.out` file, as this is now the destination for regular spans.
+Both the `agent` and `gateway` should display debug information, including the span you just sent. Additionally, the gateway should generate a new `gateway-traces-default.out` file, as this is now the destination for regular spans.
 
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
-If you verify the `./gateway-traces-default.out` is should contain the span we send with the cURL command.
+If you check `gateway-traces-default.out`, it should contain the `span` sent using the `cURL` command. You will also see an empty `gateway-traces-security.out` file, as the routing configuration creates output files immediately, even if no matching spans have been processed yet.
 {{% /notice %}}
 
 - **Send a Security Span**:  
 Make sure both the `agent` and `gateway` are running, then send a security span using the `security.json` file to test the routing rule in the gateway.  
-Both the `agent` and `gateway` should display debug information, including the span you just sent. Additionally, the gateway should generate a new `./gateway-traces-security.out` file, as this is  the destination for spans where the `deployment.environment` resourceSpan attribute matches `"security_applications"`.  
+Both the `agent` and `gateway` should display debug information, including the span you just sent. Additionally, the gateway should write  a line to the  `gateway-traces-security.out` file, as this is  the destination for spans where the `deployment.environment` resourceSpan attribute matches `"security_applications"`.  
 
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
 If you verify the `./gateway-traces-security.out` is should only contain the spans from the `"security_applications"` deployment.environment.
 {{% /notice %}}
 
+You can repeat this scenario multiple times, and each trace should be written to its corresponding output file.
+
+
 {{% /notice %}}
 
 ### Conclusion

content/en/ninja-workshops/10-advanced-otel/80-routing/_index.md

@@ -93,7 +93,6 @@ To enable routing we need to define two pipelines for traces:
         receivers: [routing]   # Only receives spans from the routing connector 
         processors:
         - memory_limiter
-        - batch
         - resource/add_mode
         exporters: [file/traces/standard] # Location for spans not matching rule
   ```
@@ -108,11 +107,11 @@ To enable routing we need to define two pipelines for traces:
         receivers: [routing]   # Only receives spans from the routing connector 
         processors:
         - memory_limiter
-        - batch
         - resource/add_mode
         exporters: [file/traces/security] # Location for spans matching rule
       #metrics:  
   ```
+  
 
 - **Update the `traces` pipeline to handle routing**:  
 To enable `routing`, you need to update the original `traces` pipeline by adding `routing` as an exporter. This will send your span data through the `routing connector` for evaluation.
@@ -127,6 +126,8 @@ To enable `routing`, you need to update the original `traces` pipeline by adding
 {{% notice title="Tip" style="primary" icon="lightbulb" %}}
 
 Keep in mind that any existing processors have been removed from this pipeline. They are now handled by either the standard pipeline or the target pipelines, depending on the routing rules.
+
+Additionally, the `batch` processor has been removed from the new pipelines. This ensures that `spans` are written immediately, rather than waiting for multiple spans to arrive before processing. This change speeds up the workshop and allows you to see results faster.
 {{% /notice %}}
 
 {{% /notice %}}