First off I would like to say that we have been working with Zabbix for a few months now as a replacement monitoring system. We had a need to unify our disparate monitoring systems, across multiple customer sites, into a central system. Zabbix has met this need, and then some. We have been very happy and you should continue to keep up the good work. We can't wait to see what 3.0 brings.
On to my issue...
We have a UserParameter script that we're using to do LLD for our custom application. The script itself is working and we are able to see valid data getting into Zabbix; both through Zabbix Server and Zabbix Proxy. However, in the instances where we use Zabbix Proxy to gather the data; it gets a little annoying because it won't actually accept "trapper" data from the script until the Proxy instance is restarted.
The template for discovery is setup to use "Zabbix agent" type for LLD; which calls our script via UserParameter.
The item prototypes are then setup as "Zabbix trapper" type.
The UserParameter script does two things: 1) It returns the discovery data back to the agent, so it knows the list of things to prototype. 2) It then sends all the prototype item data directly to the Proxy via "trapper" calls.
The issue comes up the first time our script runs, and it is specifically using a Zabbix Proxy to relay data. LLD will work, and I can see that it creates all the prototype items. However, if we go look at "Latest Data" view; you never actually see any data get populated into the items.
If we manually restart the Zabbix Proxy instance; suddenly it will start accepting the "trapper" data and everything is working fine.
I have not noticed this issue when sending data directly to the Zabbix Server instance. However, for our remote sites this is not an option and we have to relay through Zabbix Proxy.
Obviously, this work around is working for us and we are able to get our data. However, it is especially annoying when we have to restart the proxy instances every time we add this template to a new host. Any suggestions would be useful, maybe this is just a weird bug in Zabbix Proxy?
Thanks,
Kelly Shutt
On to my issue...
We have a UserParameter script that we're using to do LLD for our custom application. The script itself is working and we are able to see valid data getting into Zabbix; both through Zabbix Server and Zabbix Proxy. However, in the instances where we use Zabbix Proxy to gather the data; it gets a little annoying because it won't actually accept "trapper" data from the script until the Proxy instance is restarted.
The template for discovery is setup to use "Zabbix agent" type for LLD; which calls our script via UserParameter.
The item prototypes are then setup as "Zabbix trapper" type.
The UserParameter script does two things: 1) It returns the discovery data back to the agent, so it knows the list of things to prototype. 2) It then sends all the prototype item data directly to the Proxy via "trapper" calls.
The issue comes up the first time our script runs, and it is specifically using a Zabbix Proxy to relay data. LLD will work, and I can see that it creates all the prototype items. However, if we go look at "Latest Data" view; you never actually see any data get populated into the items.
If we manually restart the Zabbix Proxy instance; suddenly it will start accepting the "trapper" data and everything is working fine.
I have not noticed this issue when sending data directly to the Zabbix Server instance. However, for our remote sites this is not an option and we have to relay through Zabbix Proxy.
Obviously, this work around is working for us and we are able to get our data. However, it is especially annoying when we have to restart the proxy instances every time we add this template to a new host. Any suggestions would be useful, maybe this is just a weird bug in Zabbix Proxy?
Thanks,
Kelly Shutt
Comment