Support storage.total_limit_size in syslog plugin #1318
Merged
Conversation
This file contains 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
Add storage.total_limit_size to the API and CRDs to allow it to be set for the Syslog output plugin. Regenerate docs and manifests as per contributor guidelines. Signed-off-by: James King <[email protected]>
benjaminhuo
approved these changes
Aug 23, 2024
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.
What this PR does / why we need it:
This PR is to support the storage.total_limit_size parameter in the syslog output plugin. This property was introduced in Fluent Bit v1.6 and it is used for limiting the total size in bytes of chunks that can exist in the filesystem for a certain logical output destination.
Which issue(s) this PR fixes:
Fixes #1317
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: