Prepare env to work with Fluentd for TLS impl

Makefile

@@ -34,6 +34,10 @@ generate-logs:
 	./scripts/generate-logs.sh 100 >> testdata/access.log
 .PHONY:generate-logs
 
-prepare:
-	docker run -d --name fluent --rm -p 127.0.0.1:24224:24224 fluent/fluent-bit /fluent-bit/bin/fluent-bit -i forward -o stdout -p format=json_lines -f 1
-.PHONY:prepare
+run-fluentbit:
+	docker run --name fluentbit --rm -p 127.0.0.1:24224:24224 fluent/fluent-bit /fluent-bit/bin/fluent-bit -i forward -o stdout -p format=json_lines -f 1
+.PHONY:run-fluentbit
+
+run-fluentd:
+	docker run --name fluentd --rm -p 127.0.0.1:24224:24224 -v ./testdata/fluentd.conf:/fluentd/etc/fluentd.conf:ro fluent/fluentd:v1.16-debian-amd64-1 -c /fluentd/etc/fluentd.conf -v
+.PHONY:run-fluentd

README.md

@@ -17,7 +17,7 @@ git clone --recurse-submodules git@github.com:r0mdau/otelcol-dev.git
 Run a [Fluent Bit](https://fluentbit.io/) instance that will receive messages over TCP port 24224 through the [fluent-forward](https://docs.fluentbit.io/manual/pipeline/outputs/forward) protocol and send the messages to stdout interface in JSON format every second
 
 ```bash
-docker run --name fluent --rm -p 127.0.0.1:24224:24224 fluent/fluent-bit /fluent-bit/bin/fluent-bit -i forward -o stdout -p format=json_lines -f 1
+make prepare
 ```
 
 Build the custom collector
@@ -41,7 +41,7 @@ bash scripts/generate-logs.sh 100 >> testdata/access.log
 Look at Fluentbit logs
 
 ```bash
-docker logs fluent
+docker logs fluentbit
 ```
 
 ### Customize the otel modules

testdata/fluentd.conf

@@ -0,0 +1,16 @@
+<source>
+  @type  forward
+  @id    input1
+  @label @mainstream
+  port  24224
+</source>
+
+<filter **>
+  @type stdout
+</filter>
+
+<label @mainstream>
+  <match **>
+    @type stdout
+  </match>
+</label>