Hi I try my best reading all documentation about f...
# fluent-bit
d
Hi I try my best reading all documentation about fluentbit to solve one of my issues and also I am not sure if I have the correct configuration for another issue. I would like to upgrade syslog messaging input to TCP (which works correctly and is documented well), but one of my relaying parties is sending syslog messages with octet-stream, and I am not able to configure that using YAML (standard message by message syslog works correctly, but when the client sendsa burst of messages I got an error that the buffer is too small). Another issue is connected with configuring TLS for the syslog input plugin. Official documentation for YAML configuration doesn't work on version 4.0.4 however with help of ChatGPT analyzing code it is look like that TLS part need to be in transports: grupe (sever started correctly with that configuration) , but I am not sure if that is correct way or not ?
p
Can you just paste your actual config so we can see? 🙂
d
Copy code
service:
  flush: 1
  log_level: debug
  daemon: off
  http_server: off
  hot_reload: on
  parsers_file: /etc/fluent-bit/parser.yaml

pipeline: 
  inputs:
    - name: syslog
      tag: f-ticks-tcp
      parser: radni-1
      listen: 0.0.0.0
      port: 518
      buffer_chunk_size: 64000
      buffer_max_size: 900000
      receive_buffer_size: 900000
      mode: tcp
      transport:
        frame_type: octet-counted
    - name: syslog
      tag: f-ticks-tls
      parser: radni-1
      listen: 0.0.0.0
      port: 519
      buffer_chunk_size: 64000
      buffer_max_size: 900000
      receive_buffer_size: 900000
      mode: tcp
      transport: 
        tls: on
        tls.verify: on
        tls.ca_file: /etc/fluent-bit/certs/ca_syslog.crt
        tls.cert_file: /etc/fluent-bit/certs/server.crt 
        tls.key_file: /etc/fluent-bit/certs/server.key

  outputs:
    - name: stdout
      match: '*'
      format: json_lines
p
The
transport
key is not something that exists as far as I'm aware - TLS is all configured like so: https://docs.fluentbit.io/manual/administration/transport-security It's a bit non-standard YAML in that
.
is a valid key name
Which documentation is wrong? It all looks fine to me and definitely works
d
that you suggest, because if I don't use transport: group config parser wouldn't like to start service because it not recognize tls. inside of input syslog block
p
Can you clarify a bit what you mean? Your config is not valid:
Copy code
$ docker run --rm -it -v $PWD/fluent-bit.yaml:/fluent-bit/etc/fluent-bit.yaml:ro fluent/fluent-bit:4.0.4 -c /fluent-bit/etc/fluent-bit.yaml
Fluent Bit v4.0.4
* Copyright (C) 2015-2025 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

______ _                  _    ______ _ _             ___  _____ 
|  ___| |                | |   | ___ (_) |           /   ||  _  |
| |_  | |_   _  ___ _ __ | |_  | |_/ /_| |_  __   __/ /| || |/' |
|  _| | | | | |/ _ \ '_ \| __| | ___ \ | __| \ \ / / /_| ||  /| |
| |   | | |_| |  __/ | | | |_  | |_/ / | |_   \ V /\___  |\ |_/ /
\_|   |_|\__,_|\___|_| |_|\__| \____/|_|\__|   \_/     |_(_)___/ 


[2025/07/15 15:42:15] [error] could not open parser configuration file, aborting.
[2025/07/15 15:42:15] [error] [config] could not configure property 'transport' on input plugin with section name 'syslog'
[2025/07/15 15:42:15] [error] configuration file contains errors, aborting.
The
transport
key is not a valid key. Also
tls.cert_file
should be
tls.crt_file
.
This runs up for me:
Copy code
pipeline: 
  inputs:
    - name: syslog
      tag: f-ticks-tls
      parser: radni-1
      listen: 0.0.0.0
      port: 519
      buffer_chunk_size: 64000
      buffer_max_size: 900000
      receive_buffer_size: 900000
      mode: tcp
      tls: on
      tls.verify: on
      tls.ca_file: /etc/fluent-bit/certs/ca_syslog.crt
      tls.crt_file: /etc/fluent-bit/certs/server.crt 
      tls.key_file: /etc/fluent-bit/certs/server.key
Can't say it's working but it's not invalid.
If you want to see the options actually supported for sure:
Copy code
$ docker run --rm -it fluent/fluent-bit:4.0.4 -i syslog --help
...
NETWORK_TLS
tls                                Enable or disable TLS/SSL support
                                   > default: off, type: boolean

tls.verify                         Force certificate validation
                                   > default: on, type: boolean

tls.debug                          Set TLS debug verbosity level. It accept the following
                                   values: 0 (No debug), 1 (Error), 2 (State change), 3
                                   (Informational) and 4 Verbose
                                   > default: 1, type: integer
...
Make sure you're on the latest version (4.0.4) of OSS Fluent Bit, not another version or from AWS, etc.
if I don't use transport: group config parser wouldn't like to start service because it not recognize tls. inside of input syslog block
What's this
config parser
you mention?
d
faund 🙂 ... error message is misleading
Copy code
[2025/07/15 16:00:37] [error] [config] syslog: unknown configuration property 'tls.cert_file'. The following properties are allowed: mode, path, unix_perm, buffer_chunk_size, buffer_max_size, parser, receive_buffer_size, raw_message_key, and source_address_key.
what exactly issue was naming
tls.cert
vs
tls.crt
p
Yeah, the error message only prints out the specific config options from the plugin - the TLS ones are generic ones inherited. If you want to see the full ones then run
-i <plugin name> --help
d
additionaly to that is version which was 4.0.2. where transport group work and probably ignore all configuration parameters inside
when start 4.0.4 transport group was labeled like error
removed like you sugested and now everything is working
p
I'm still confused, transport group is not supported by anything but it looks like for 4.0.2 there is a separate problem with parsers - your config does not run for me:
Copy code
$ docker run --rm -it -v $PWD/fluent-bit.yaml:/fluent-bit/etc/fluent-bit.yaml:ro fluent/fluent-bit:4.0.2 -c /fluent-bit/etc/fluent-bit.yaml
...
[2025/07/15 16:07:21] [error] [config] could not configure property 'transport' on input plugin with section name 'syslog'
However, glad you got it sorted
d
I will try with option for plugin like you suggested to see if I can solve my other issue with syslog block of messages
thanks for help