I have an issue with the metricset Queue for RabbitMQ. If there are 1 or more consumers on a queue, there is no problem. Then metrics from this queue comes in Elasticsearch.
As soon as the consumer disappears, no more metric enters the Elasticsearch. Even though there are still messages coming in on this queue.
The ideal would be that every 10 seconds (in my case) an update of all queues is forwarded to Elasticsearch. Such as what is the case with the metricset Exchange.
- module: rabbitmq metricsets: - node - queue - exchange - connection enabled: true period: 10s hosts: ["localhost:15672"]
This is very annoying because we then have no idea that there is a problem with this queue because messages are filling up because there is no consumer. Then this should be visually in Kibana, which is not possible now.
I use the following versions:
- RabbitMQ 3.7.9
- Erlang 21.1
- Metricbeat 7.1.1
Can anyone help me?