If Fluentbit is set up to log out to a file, and then also set up with a tail input on that file, in debug mode, a tonne of events get logged in a loopback manner.
Sample config:
[SERVICE]
Log_File /tmp/fluentbit.log
[INPUT]
Name tail
Path /tmp/fluentbit.log
Tag ouroborous
[INPUT]
Name dummy
[OUTPUT]
Name stdout
Match *
It'd be great if this tail event debug logging were selectively disabled for any tail inputs that happen to be targeting the same file that Fluentbit itself is writing logs out to, so that debug logging mode was still able to be used for useful debugging when loopback-logging like this is in place.
If Fluentbit is set up to log out to a file, and then also set up with a
tail
input on that file, in debug mode, a tonne of events get logged in a loopback manner.Sample config:
Sample output:
It'd be great if this tail event debug logging were selectively disabled for any tail inputs that happen to be targeting the same file that Fluentbit itself is writing logs out to, so that debug logging mode was still able to be used for useful debugging when loopback-logging like this is in place.