AMQP source: Support automatic recovery from a broken connection

[amanmahajan26]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Use Cases

We recently switched from Logstash to Vector for consuming messages from RabbitMQ using the AMQP source. While the pipeline works fine, whenever we make changes to our RabbitMQ nodes like upscaling or downscaling, the connection gets broken and Vector needs to be restarted to start consuming messages again. In Logstash, there is a automatic_recovery feature (https://www.elastic.co/guide/en/logstash/7.17/plugins-inputs-rabbitmq.html#plugins-inputs-rabbitmq-automatic_recovery) due to which such restart is not required. Would be nice to have this feature available for Vector AMQP source as well.

Configuration:

[sources.raw_amqp] type = "amqp" connection_string = "" exchange_key = "queue" queue = ""

Attempted Solutions

No response

Proposal

No response

References

No response

Version

0.37.1

[jszwedko]

Thanks @amanmahajan26 ! Vector should definitely recover in these situations.