Document the storage.backlog.flush_on_shutdown Fluent Bit buffer option - #344
Open
promptless-for-oss wants to merge 1 commit into
Conversation
Add a Buffering subsection covering the new opt-in BufferStorage option that flushes filesystem-backlog chunks on graceful shutdown, avoiding buffered-record loss on node drain or spot reclaim (logging-operator #2282).
csatib02
marked this pull request as ready for review
July 31, 2026 18:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Open this suggestion in Promptless to view citations and reasoning process
Fluent Bit can now flush filesystem-backlog chunks to their destination during a graceful shutdown through the new opt-in
storage.backlog.flush_on_shutdownfield on theBufferStoragespec. Without it, buffered records are lost when a node is drained or a spot instance is reclaimed.This adds a "Flush the filesystem buffer on shutdown" subsection to the Buffering section of the Fluent Bit log collector page (
content/docs/logging-infrastructure/fluentbit.md). It explains the option, itsOn/Offvalues andOffdefault, the filesystem-buffering prerequisite, and aFluentbitAgentexample, and cross-referencesterminationGracePeriodSecondsso the pod has time to finish flushing. The generated CRD reference page picks up the field automatically on the next upstream sync, so it is intentionally left untouched here.Trigger Events