With old config format, it was possible tu uses wi...
# fluent-bitt
Thomas Guenneguez
10/15/2025, 9:14 AMWith old config format, it was possible tu uses wildcard characters :
Copy code
@INCLUDE input_*.confp
Pat
10/15/2025, 9:22 AMDid you quote the string? Normally that's a YAML special
Pat
10/15/2025, 9:25 AM*Pat
10/15/2025, 9:27 AMThe YAML spec says that it is an alias for an anchor, although the config spec does not support anchors I bet the YAML parser still copes with the syntax: https://yaml.org/spec/1.2.2/#alias-nodes
t
Thomas Guenneguez
10/15/2025, 9:29 AMHello,
No, I haven't tested it in YAML, but I'm reading the documentation and I see there's no example.
I may have wrongly concluded that it wasn't possible.
I'll try when I have some time.
If it's possible, it would be nice to add it to the documentation.
Thanks,
Thomas
p
Pat
10/15/2025, 9:30 AMSure, the docs are all OSS so feel free to raise a PR for it: https://github.com/fluent/fluent-bit-docs
Pat
10/15/2025, 9:33 AMNote that wildcard inclusion has some potential pitfalls - there is no guarantee of order which can cause problems even with the same config being loaded in different orders: https://github.com/fluent/fluent-bit/issues/5612
It may not affect you right now but it is something to be aware of - that was a fun time debugging pods in K8S for me 🙂
t
Thomas Guenneguez
10/15/2025, 9:35 AMHello, Indeed, we just noticed this with the use of the Add primitive of the modify filter. So we switch to Set.
p
Pat
10/15/2025, 9:36 AMYeah, never rely on order is a good strategy in general. If you need ordering then make it in the file not by includes - or have specific includes in order