chore: change chunks dropped log level. #11273
Open
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.
Changing the
log_levelfor messages about chunks being dropped, to'info'.Fixes: [N/A]
Doesn't address a particular issue. (at least I did'n find one)
Documentation
Currently, it's difficult to detect when the
storage.total_limit_sizeis reached (and react accordingly), as nothing is logged, unless the log level is set todebug, which makes the output noisy.Maybe there is some way to log something, but I didn't manage to find one.
Please write if a
Valgrindreport is still needed.I would expect the
log_infoto be tested already.Backporting
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.