Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

ERROR at monitoring specific queues with discovery rules. #107

Open
dmorais895 opened this issue Sep 24, 2019 · 1 comment
Open

ERROR at monitoring specific queues with discovery rules. #107

dmorais895 opened this issue Sep 24, 2019 · 1 comment

Comments

@dmorais895
Copy link

Hi,

We are trying to use your solution, and we are getting some success. But, when we try to monitor an specific queue with the discovery rule, this happen:

2019-09-24 16:52:42,524 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,524 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,525 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,525 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,525 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,525 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,526 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_memory,queueName]" 36860
2019-09-24 16:52:42,526 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_messages,queueName]" 24
2019-09-24 16:52:42,526 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_messages_unacknowledged,queueName]" 0
2019-09-24 16:52:42,526 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_consumers,queueName]" 0
2019-09-24 16:52:42,526 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_message_stats_deliver_get,queueName]" 141
2019-09-24 16:52:42,527 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_message_stats_publish,queueName]" 98
2019-09-24 16:52:42,527 DEBUG: SENDER_DATA: - "rabbitmq.queues[/,queue_message_stats_ack,queueName]" 18
2019-09-24 16:52:42,527 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,527 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,527 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,528 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,528 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,528 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,528 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,528 DEBUG: Filtering out by [{u'name': u'queueName'}]
2019-09-24 16:52:42,543 DEBUG: Finished sending data
2019-09-24 16:52:42,544 INFO: Found return code of 2
2019-09-24 16:52:42,544 DEBUG: zabbix_sender [20354]: DEBUG: answer [{"response":"success","info":"processed: 0; failed: 7; total: 7; seconds spent: 0.000133"}]

2019-09-24 16:52:42,544 DEBUG: info from server: "processed: 0; failed: 7; total: 7; seconds spent: 0.000133"
sent: 7; skipped: 0; total: 7

Then, this trigger is appears:
No data received on queue //queueName in 10 minutes.
So, we realize that no data has been received by the server. But de log output, show us that de metrics are successful coleted.

Can you help to understand the problem?

@jasonmcintosh
Copy link
Owner

They're collected, but failed to send, which often means the remote side doesn't have the queues. I apologize for delays in response, but I no longer work on zabbix or rabbitmq in any form, so I won't be able to assist much :(

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants