i don't know if i've found a bug or if it is my ya...
# fluent-bit
p
i don't know if i've found a bug or if it is my yaml syntax knowledge that's the culprit in
classic
configuration format it was possible to write something like:
Copy code
[FILTER]
  name modify
  match_regex .*(cloudnative-pg).*
  remove 'started at'
in yaml format i suppose it should look like:
Copy code
---
pipeline:
  filters:
    - name: modify
      match_regex: '.*(cloudnative-pg).*'
      remove: 'started at'
but this will generate an error:
Copy code
[2025/08/01 05:00:15] [error] [filter:modify:modify.13] Invalid operation remove : started at in configuration
[2025/08/01 05:00:15] [error] Failed initialize filter modify.13
[2025/08/01 05:00:15] [error] [engine] filter initialization failed
is this a bug or is it just me? šŸ˜…
i don't understand creating logs with a key name including a space but i've reported it as a bug at cloudnative-pg also https://github.com/cloudnative-pg/cloudnative-pg/issues/8205
e
@Patric Buskas I am able to reproduce your observation. What works is
remove_regex: /started\sat/
p
thank you @emmacz šŸ™ i already got a fix from cloudnative-pg but this knowledge is good to know and what we'll have to use until the issue is fixed in next release of cnpg
p
I recall seeing an issue maybe due to a reserved word for the key remove
e
@Patric Buskas np. Looks like there are many differences between classic and yaml format. šŸ˜ž This will be good topic for some enthusiast to remove them. šŸ™‚ • In classic format .. ā—¦ Modify f. accepts Keys with space, in yaml not ā—¦ Classic format does not accept parsers inside ā—¦ Quotes is always challenge .. which one (single or double) to use or not use in what format
@Pat ^^^ maybe you know someone who can take it and fix it šŸ™‚
p
i'm just happy to have found an issue that will improve fluent-bit šŸŽ‰ thank you all for your help and sharing mindset ā¤ļø
šŸ‘ 1
p
Yaml format should accept the exact same config classic does, however there are some constraints from yaml itself like quoting required for special characters, etc
p
yes, that's for sure but just quoting doesn't help in this case
p
Yeah I think there were some other things we found, just more an example. In general, the config keys can be identical so weird if it's not