Skip to content

Commit db2a70b

Browse files
committed
Added stop instruction for the files running to all previous section
1 parent df82d86 commit db2a70b

File tree

3 files changed

+15
-4
lines changed

3 files changed

+15
-4
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -395,4 +395,5 @@ Now the gateway should have generated a new file called `./gateway-traces.out`
395395

396396
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"`
397397

398-
We will correct that in a later section.
398+
We will correct that in a later section.
399+
Stop the Agent and Gateway that are running using `Command-c/Ctrl-c`.

content/en/ninja-workshops/10-advanced-otel/30-filelog/1-agent-filelog.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,3 +223,5 @@ Note that the `resoureLogs` section contains the same attributes as we saw in `t
223223

224224
{{% /tab %}}
225225
{{% /tabs %}}
226+
227+
Stop the Agent, Gateway and the Quotes generating script as well using `Command-c/Ctrl-c`.

content/en/ninja-workshops/10-advanced-otel/30-filelog/_index.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,15 @@ time: 10 minutes
55
weight: 3
66
---
77

8-
The Filelog receiver is a receiver that reads log lines from a file. It is useful for testing and development purposes. The Filelog receiver is not recommended for production use, as it is not optimized for performance but can be useful in a pinch. For this part of the workshop, there is script that will generate log lines in a file. The Filelog receiver will read these log lines and send them to the OpenTelemetry Collector.
8+
The `FileLog` receiver in the OpenTelemetry Collector is used to ingest logs from files. It monitors specified files for new log entries and streams those logs into the Collector for further processing or exporting. It is useful for testing and development purposes.
99

10-
Create a new sub directory called `3-filelog` and copy the content from `2-gateway` across. Delete any `*.out` files and create the appropriate log generation script for your operating system in the new directory (`log-gen.sh` on Mac or Linux or `log-gen.ps1` for Windows), make sure its executable.
10+
The Filelog receiver is not recommended for production use, as it is not optimized for performance but can be useful in a pinch. For this part of the workshop, there is script that will generate log lines in a file. The Filelog receiver will read these log lines and send them to the OpenTelemetry Collector.
11+
12+
### Setup
13+
14+
Create a new sub directory called `3-filelog` and copy the content from `2-gateway` across. Delete any `*.out` files.
15+
16+
Copy one of the two version below and create the appropriate log generation script for your operating system in the new directory (`log-gen.sh` on Mac or Linux or `log-gen.ps1` for Windows). Make sure its executable.
1117

1218
Once we started the log-gen script the directory structure will look like this:
1319

@@ -132,8 +138,10 @@ while ($true) {
132138
{{% /tab %}}
133139
{{% /tabs %}}
134140

135-
Run the new log generating script and it will start writing lines to a file called `./quotes.log`, and the console output a single line:
141+
Run the new log generating script in its own shell and it will start writing lines to a file called `./quotes.log`, and the console output a single line:
136142

137143
```txt
138144
Writing logs to quotes.log. Press Ctrl+C to stop.
139145
```
146+
147+
Leave it running.

0 commit comments

Comments
 (0)