Dustin C. Hatch
6ad76e4b33
Fluent Bit supports including configuration fragments from other files using its `includes` option. Adding a glob pattern to the default configuration will allow other roles to supply additional configuration by creating files in the `/etc/fluent-bit/include` directory. This makes composition of configuration significantly easier. Unfortunately, `fluent-bit` has a quirk in that there must exist at least one file matching the glob pattern, or it will fail to start. To work around this, we must supply an empty fragment.
43 lines
917 B
YAML
43 lines
917 B
YAML
fluent_bit_config:
|
|
includes:
|
|
- /etc/fluent-bit/include/*.yml
|
|
service: '{{ fluent_bit_config_service }}'
|
|
parsers: '{{ fluent_bit_parsers }}'
|
|
multiline_parsers: '{{ fluent_bit_multiline_parsers }}'
|
|
pipeline: '{{ fluent_bit_pipeline }}'
|
|
|
|
fluent_bit_config_service:
|
|
log_level: '{{ fluent_bit_log_level }}'
|
|
|
|
fluent_bit_log_level: info
|
|
|
|
fluent_bit_pipeline:
|
|
inputs: '{{ fluent_bit_inputs }}'
|
|
filters: '{{ fluent_bit_filters }}'
|
|
outputs: '{{ fluent_bit_outputs }}'
|
|
|
|
fluent_bit_inputs: '{{ fluent_bit_default_inputs }}'
|
|
|
|
fluent_bit_default_inputs:
|
|
- '{{ fluent_bit_input_systemd }}'
|
|
|
|
fluent_bit_input_systemd:
|
|
name: systemd
|
|
tag: host.*
|
|
db: /var/lib/fluent-bit/journal
|
|
lowercase: true
|
|
strip_underscores: true
|
|
|
|
fluent_bit_parsers: []
|
|
|
|
fluent_bit_multiline_parsers: []
|
|
|
|
fluent_bit_filters: []
|
|
|
|
fluent_bit_outputs:
|
|
- '{{ fluent_bit_null_output }}'
|
|
|
|
fluent_bit_null_output:
|
|
name: null
|
|
match: '*'
|