Tags: logstash-plugins/logstash-integration-rabbitmq
Tags
Fixed the cancellation flow to avoid multiple invocations of basic.ca… …ncel (#55) This commit adds an extra condition on the consumer shutdown to check whether the client is already canceled/terminated by the broker or if it should execute the plugin cancellation flow calling the channel.basic_cancel(@consumer.consumer_tag) and waiting for the consumer to terminate.
Refactor: logging improvements (#47) Currently the plugin does not gather logs from the underlying RabbitMQ library in LS' log. Some debug logging by the frontend (MarchHare) could be accessed (w an env property) but ends up on STDERR. This PR integrates the underlying logging to be part of LS' logging mechanism.
Doc:Replace plugin_header file with plugin_header-integration file (#34) Integration plugins need a header that is different from the stand-alone plugin header. The plugin docs links should point to the integration repo rather than the stand-alone input and output repos. The header also adds a note that the plugin is part of an integration rather than stand-alone.
release 7.1.0 (#33) * release 7.1.0 - Added support in Output plugin for sprintf templates in values provided to message_properties (#8) - Added support for extended metadata including raw payload to events generated by the Input Plugin (#13) - Fixes an issue with custom port assignment, in which the custom port was not being applied when more than one host was supplied (#12) - Fixes bug where attempting to read from undeclared exchange resulted in infinite retry loop (#10) - Fixes bug where failing to establish initial connection resulted in a pipeline that refused to shut down (#11) - Docs: add hint about queue durability settings in input needing to match those of the existing queue Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
PreviousNext