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
Problem
It seems that disabling sinks healthcheck via setting --require-healthy flag to false on startup has no effect when sink type is amqp and no vhost is specified in amqp connection_string, or the vhost does not exist at all.
I tried setting wrong port on other sink types like kafka and elasticsearch and it didn't cause vector to crash so I presume what I'm reporting should be a bug related to amqp sink or the way vector is using it.
A note for the community
Problem
It seems that disabling sinks healthcheck via setting
--require-healthy
flag tofalse
on startup has no effect when sink type isamqp
and no vhost is specified in amqpconnection_string
, or the vhost does not exist at all.Same thing happens when connection string points to a wrong port:
I tried setting wrong port on other sink types like
kafka
andelasticsearch
and it didn't cause vector to crash so I presume what I'm reporting should be a bug related toamqp
sink or the way vector is using it.Configuration
Version
vector 0.34.1 (x86_64-unknown-linux-gnu 86f1c22 2023-11-16 14:59:10.486846964)
Debug Output
Example Data
No response
Additional Context
vector is installed with apt and rabbitmq is up on port 5672 with following docker-compose deployment:
References
No response