Skip to content

Commit 27228ad

Browse files
committed
Markdown linting
1 parent 3dc0ea2 commit 27228ad

File tree

3 files changed

+5
-6
lines changed

3 files changed

+5
-6
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ Open our agent.yaml in your editor and let's add the `OTLP/HTTP` exporter to the
2828

2929
{{% notice title="Exercise" style="green" icon="running" %}}
3030

31-
- Add `otlphttp:` under the `exporter:` key
32-
- Add `endpoint:` key and set it to a value of `"http://localhost:5318"` * note that we use the port of the gateway
31+
- Add `otlphttp:` under the `exporter:` key
32+
- Add `endpoint:` key and set it to a value of `"http://localhost:5318"` * note that we use the port of the gateway
3333
- Add `headers:` key
3434
- Add `X-SF-Token:` key and set it with a fake access token like `"FAKE_SPLUNK_ACCESS_TOKEN"`
3535

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -260,12 +260,11 @@ Next, make sure both the gateway and the agent are running in their own shell, t
260260
```sh
261261
curl -X POST -i http://localhost:4318/v1/traces \
262262
-H "Content-Type: application/json" \
263-
-d @trace.json
263+
-d @trace.json
264264
```
265265

266266
Now the gateway should have generated a new file called `./gateway-traces.out` and it should contain the following trace:
267267

268-
269268
{{% tabs %}}
270269
{{% tab title="Compacted JSON" %}}
271270

@@ -360,4 +359,4 @@ Now the gateway should have generated a new file called `./gateway-traces.out`
360359

361360
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"`
362361

363-
We will correct that in a later section.
362+
We will correct that in a later section.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,4 @@ weight: 7
77

88
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.
99

10-
![Routing Processor](../images/routing.png)
10+
![Routing Processor](../images/routing.png)

0 commit comments

Comments
 (0)