Added possibility for a custom internal log handler injection #9302
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it's required to collect internal Fluent Bit logs inside an application that uses it as a library.
Unfortunately, Fluent Bit only properly supports logging to a file (that is slow and the implementation is very simple since the file is not ever rotated) and to stderr (that mixes with other stderr messages and cannot be properly handled inside an application when the Fluent Bit is used as a library).
This PR adds a configuration parameter that allows library clients to override this behavior by providing their custom internal logs handling function
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.