RabbitMQ Scaler doesn't complain if there is no queue info #7180
Description
Proposal
It would be helpful if the RabbitMQ scaler printed an error if the JSON response from the RabbitMQ api doesn't include any queue stats.
Reason:
We recently migrated away from the Bitnami RabbitMQ helm chart, which enables rabbitmq_management by default and accidentally installed the version without the management plugin.
We soon realized that, even though we have queues with messages in them, KEDA wouldn't prompt K8S to start any new pods. This was especially problematic since we have scale-to-zero enabled, which disrupted operations as there were zero pods consuming the messages.
After a bit of cURLing, we noticed that the JSON response from the RabbitMQ api didn't include any stats about the queues, and from the scaler code it seems like the queue is treated as having 0 messages, if the messages field is not in the JSON response.
Use-Case
An error indicating something like "Couldn't read queue stats for X queue" would help to verify if the scaler is getting the correct information from RabbitMQ.
Is this a feature you are interested in implementing yourself?
Maybe
Anything else?
No response