Cherry-pick #21993 to 7.x: [Filebeat] Add max_number_of_messages config parameter for S3 input #22035
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.
Cherry-pick of PR #21993 to 7.x branch. Original message:
What does this PR do?
This PR adds
max_number_of_messages
config option for S3 input to control the number of SQS messages returning from eachReceiveMessage
API call.Why is it important?
This will help to debug performance issues since this controls how many messages returned once and how many log files will be processed in parallel together.
Checklist
[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.