You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you add a conf file to the config.extraFiles field in values.yaml, the file is correctly created and added to the fluentbit container, however, no @INCLUDE statement is dynamically added to the fluent-bit.conf to allow the config data to actually be seen and used. If you want it to be used you have to override the config.service value manually.
Additionally, there isn't a way to add custom parsers as a parser file. You can only define them directly in the config.customParsers field. Just like the extraFiles field, we should add a parserFiles field to allow the submission of additional parsers files. This will allow the dynamic addition of additional parsers following a similar and consistent format to conf files. This will require the creation of the parserFiles field as well as ensuring that those files then get proper references in the fluent-bit.conf file.
The text was updated successfully, but these errors were encountered:
@justin.vandiver this issue has been inactive for 30 days and is being labelled as ~stale. If this issue is still required please take action by removing the ~stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as ~delete-me. If no action is taken this issue will be auto closed in 60 days.
Currently if you add a conf file to the
config.extraFiles
field invalues.yaml
, the file is correctly created and added to the fluentbit container, however, no@INCLUDE
statement is dynamically added to thefluent-bit.conf
to allow the config data to actually be seen and used. If you want it to be used you have to override theconfig.service
value manually.Additionally, there isn't a way to add custom parsers as a parser file. You can only define them directly in the
config.customParsers
field. Just like theextraFiles
field, we should add aparserFiles
field to allow the submission of additional parsers files. This will allow the dynamic addition of additional parsers following a similar and consistent format to conf files. This will require the creation of the parserFiles field as well as ensuring that those files then get proper references in thefluent-bit.conf
file.The text was updated successfully, but these errors were encountered: