Add support for max_inbound_message_body_size parameter. Fixes #59 #62
Conversation
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
|
Could you assist with investigating the https://app.travis-ci.com/github/logstash-plugins/logstash-integration-rabbitmq/jobs/634058900 job failure? The error suggests lack of a Docker image related to future builds of logstash version 8 so it seems to be unrelated with the pull request as the images seem to be created by logstash. Regarding the job https://app.travis-ci.com/github/logstash-plugins/logstash-integration-rabbitmq/jobs/634058893 I still investigate the issue. |
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.
Hi,
This pull request adds a possibility for a logstash user to configure maximum inbound message body size for messages fetched from a RabbitMQ queue by logstash above (or below) the default limit of the RabbitMQ connector - 67108864 bytes - currently set as a not configurable default by logstash.
Therefore it fixes issue #59.
Best regards
mp107