Merge remote-tracking branch 'refs/remotes/origin/main'

Author: jelkhouri-splunk

content/en/ninja-workshops/10-advanced-otel/20-gateway-setup/1-gateway-test.md

@@ -28,8 +28,8 @@ Open our agent.yaml in your editor and let's add the `OTLP/HTTP` exporter to the
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-  - Add `otlphttp:` under the `exporter:` key
-    - Add `endpoint:` key and set it to a value of `"http://localhost:5318"`   *  note that we use the port of the gateway
+- Add `otlphttp:` under the `exporter:` key
+  - Add `endpoint:` key and set it to a value of `"http://localhost:5318"`   *  note that we use the port of the gateway
     - Add `headers:` key
       - Add `X-SF-Token:` key and set it with a fake access token like `"FAKE_SPLUNK_ACCESS_TOKEN"`  
 

content/en/ninja-workshops/10-advanced-otel/20-gateway-setup/2-test-agent-gateway.md

@@ -260,12 +260,11 @@ Next, make sure both the gateway and the agent are running in their own shell, t
 ```sh
 curl -X POST -i http://localhost:4318/v1/traces \
 -H "Content-Type: application/json" \
- -d @trace.json 
+-d @trace.json 
 ```
 
 Now the gateway should have generated a new file  called `./gateway-traces.out`  and it should contain the following trace:
 
-
 {{% tabs %}}
 {{% tab title="Compacted JSON" %}}
 
@@ -360,4 +359,4 @@ Now the gateway should have generated a new file  called `./gateway-traces.out`
 
 Note that both the `./gateway-metrics.out` and the `./gateway-traces.out`  have a resource metric/attribute key  `"otelcol.service.mode"` with a value of `"agent"`
 
-We will correct that in a later section.  
+We will correct that in a later section.

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

@@ -7,4 +7,4 @@ weight: 7
 
 The routing processor allows you to route data to different destinations based on the attributes of the data. The routing processor can be used to send data to different backends based on the attributes of the data. For example, you can use the routing processor to send data to different backends based on the service name or the environment.
 
-![Routing Processor](../images/routing.png)
+![Routing Processor](../images/routing.png)