Closed ghost closed 6 years ago
Bleh one of my releases was supposed to have fixed this... will dig. Should be able to tweak your alert though on this one. Think I recall it being > 2 to trigger an error.
https://github.com/jasonmcintosh/rabbitmq-zabbix/issues/50
Yep - thought I'd fixed this... can dig again...
Note with latest release I've changed the status code check to look for a COMPLETE failure, not just a partial failure (zabbix_sender code of 1 is complete failure, 2 is partial failure, e.g. filtered queues). This should help - if no updates here in a few weeks I'll close this out :)
The template file has:
for Queue data status issue
2018-02-05 20:36:52,843 DEBUG: Filtering out by [{}] 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_memory,skype_tasks]" 101752 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_messages,skype_tasks]" 42 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_messages_unacknowledged,skype_tasks]" 0 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_consumers,skype_tasks]" 0 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_message_stats_deliver_get,skype_tasks]" 0 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_message_stats_publish,skype_tasks]" 0 2018-02-05 20:36:52,843 DEBUG: SENDER_DATA: - "rabbitmq.queues[sl-task-manager,queue_message_stats_ack,skype_tasks]" 0 2018-02-05 20:36:52,853 DEBUG: Finished sending data 2018-02-05 20:36:52,854 INFO: Found return code of 2 2018-02-05 20:36:52,854 DEBUG: zabbix_sender [20759]: DEBUG: answer [{"response":"success","info":"processed: 0; failed: 217; total: 217; seconds spent: 0.002549"}]
2018-02-05 20:36:52,854 DEBUG: info from server: "processed: 0; failed: 217; total: 217; seconds spent: 0.002549" sent: 217; skipped: 0; total: 217
DEBUG: Filtering out by [{}] - its my problem? How to disable filtering?
Filtering of [{}] means no filters applied. SO you're not actually filtering anything. 217 items failed because the server failed them vs. the client (looks like). USUALLY that means auto discovery hasn't found everything or isn't running.
Hello!
[root@sl-api rabbitmq]# zabbix_agentd -t rabbitmq[queues] rabbitmq[queues] [t|2]
[root@sl-api rabbitmq]# ./rabbitmq-status.sh queues 2
And I have "Queue data status issue" triggered...