{"action":"created","issue":{"url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/18","labels_url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/18/comments","events_url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/18/events","html_url":"https://github.com/jasonmcintosh/rabbitmq-zabbix/issues/18","id":63842206,"number":18,"title":"rabbitmq-status.sh not working","user":{"login":"whitbrett","id":11620593,"avatar_url":"https://avatars.githubusercontent.com/u/11620593?v=3","gravatar_id":"","url":"https://api.github.com/users/whitbrett","html_url":"https://github.com/whitbrett","followers_url":"https://api.github.com/users/whitbrett/followers","following_url":"https://api.github.com/users/whitbrett/following{/other_user}","gists_url":"https://api.github.com/users/whitbrett/gists{/gist_id}","starred_url":"https://api.github.com/users/whitbrett/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitbrett/subscriptions","organizations_url":"https://api.github.com/users/whitbrett/orgs","repos_url":"https://api.github.com/users/whitbrett/repos","events_url":"https://api.github.com/users/whitbrett/events{/privacy}","received_events_url":"https://api.github.com/users/whitbrett/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-23T21:52:21Z","updated_at":"2015-04-09T14:34:35Z","closed_at":null,"body":"First, Let me state that this is really good stuff.  I believe that I have found a issue, but need to have someone else look at it for me.\r\n\r\nI am having issues with getting the information about the queues out of the system.  I have been tracing data all day, and here is what I can see.  I am not sure if I have this right, but it applies to the discovery rules.  \r\n\r\nCurrently, my system will query and get all the queues that are on the server.  \r\nboth list_rabbit_nodes.sh and list_rabbit_queues.sh work just fine.  They are reporting back to zabbix with no issues.\r\n\r\nThe issue is when it goes to pull the information from the server about the queues that are on the server.\r\n\r\nI noticed that on one of the discovery trigger templates,  rabbitmq[{#VHOSTNAME},queue_messages,{#QUEUENAME}] is used to get the messages on the queue.\r\n\r\nThis will call rabbitmq-status.sh in the directory.  The issue I believe is the placing of the variables.\r\nUserParameter=rabbitmq[*],/etc/zabbix/scripts/rabbitmq/rabbitmq-status.sh $1 $2 $3\r\nThat would put $1 = VHOST NAME, $2 = queue_messages, and $3 = the queue name.\r\n\r\nThis will then get passed to the api.py like the following:\r\n/api.py --hostname=localhost.localdomain --username=admin --password=admin --check=vhost67.232.139.140 --metric=queue_messages --node=qi67.232.139.140radiodix --filters= --conf=/etc/zabbix/zabbix_agent.conf\r\n\r\nWhich will then return a error:\r\n\r\napi.py: error: option --check: invalid choice: 'vhost67.232.139.140' (choose from 'list_queues', 'list_nodes', 'queues', 'check_aliveness', 'server')\r\n\r\nFirst thing that I can see is that there is not check for just a vhost.  Also, there is no matric for queue_messages...\r\n\r\n\r\nAm I missing something here...  \r\n\r\nAll I want to get is the number of messages in the queue and have a trigger on it when it goes over a number that we set.\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/comments/91249536","html_url":"https://github.com/jasonmcintosh/rabbitmq-zabbix/issues/18#issuecomment-91249536","issue_url":"https://api.github.com/repos/jasonmcintosh/rabbitmq-zabbix/issues/18","id":91249536,"user":{"login":"whitbrett","id":11620593,"avatar_url":"https://avatars.githubusercontent.com/u/11620593?v=3","gravatar_id":"","url":"https://api.github.com/users/whitbrett","html_url":"https://github.com/whitbrett","followers_url":"https://api.github.com/users/whitbrett/followers","following_url":"https://api.github.com/users/whitbrett/following{/other_user}","gists_url":"https://api.github.com/users/whitbrett/gists{/gist_id}","starred_url":"https://api.github.com/users/whitbrett/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitbrett/subscriptions","organizations_url":"https://api.github.com/users/whitbrett/orgs","repos_url":"https://api.github.com/users/whitbrett/repos","events_url":"https://api.github.com/users/whitbrett/events{/privacy}","received_events_url":"https://api.github.com/users/whitbrett/received_events","type":"User","site_admin":false},"created_at":"2015-04-09T14:34:35Z","updated_at":"2015-04-09T14:34:35Z","body":"We have had to look at doing out own implementation. \nI was not able to get the information to work in the system. \n\nThanks for being willing to help on this though. \n\nKind Regards, \n\nBrett Whittacre \nVice President \nwhit@ec2software.com \nec 2 Software Solutions \n3035 E. Patrick \nSte. 1 \nLas Vegas, Nevada, 89120 \nP : 1.866.791.3673 ext 200 | F: 1.702.947.7357 \nwww.ec2software.com \nFollow the rules. Exceed the standard . \n\n----- On Apr 8, 2015, at 5:06 PM, Jason <notifications@github.com> wrote: \n\n> Get things figured out on this?\n\n> —\n> Reply to this email directly or view it on GitHub .\n"}}