Hello Everyone,
We've been attempting to monitor some web applications with the zabbix_proxy agent on a remote server. The situation is a little tricky because the proxy is running inside a private network and does not directly have any access to the internet or the network where the zabbix_server resides.
We have a workaround in order to get the zabbix_proxy agent to communicate with the main zabbix_server, and have determined that the proxy is able to phone home and receive updates. The problem here is that when we add a new application/httpsteps to the host which is monitored by our proxy no matter what we try to do, our zabbix_server tries to curl the URL we have given it, instead of the actual zabbix_proxy. Since all of the sites we are trying to hit are not publicly available, it fails every single time.
I've done some database diving and have come to the conclusion that zabbix_server is not sending the instructions off to the zabbix_proxy. All of the database tables relating to http steps and items remain blank. In a previous post in the forums it was mentioned that the zabbix_proxy should be able to perform the web monitoring, you're even told to compile the proxy agent with libcurl.
I've configured the proxy to phone home, added the proxy host in to the main database, and as far as I can tell there are no other options to set unless I want to work in a node based environment. Since two way communication is unavailable in our configuration this is impossible. One thing to note is that I _am_ able to tell the proxy to monitor remote hosts, so there is configuration data being passed and that portion is indeed functional. Does anyone have suggestions or ideas as to what the issue here may be? We are running both systems with CentOS 5 and Zabbix server / agent 1.6.1
-Sean
We've been attempting to monitor some web applications with the zabbix_proxy agent on a remote server. The situation is a little tricky because the proxy is running inside a private network and does not directly have any access to the internet or the network where the zabbix_server resides.
We have a workaround in order to get the zabbix_proxy agent to communicate with the main zabbix_server, and have determined that the proxy is able to phone home and receive updates. The problem here is that when we add a new application/httpsteps to the host which is monitored by our proxy no matter what we try to do, our zabbix_server tries to curl the URL we have given it, instead of the actual zabbix_proxy. Since all of the sites we are trying to hit are not publicly available, it fails every single time.
I've done some database diving and have come to the conclusion that zabbix_server is not sending the instructions off to the zabbix_proxy. All of the database tables relating to http steps and items remain blank. In a previous post in the forums it was mentioned that the zabbix_proxy should be able to perform the web monitoring, you're even told to compile the proxy agent with libcurl.
I've configured the proxy to phone home, added the proxy host in to the main database, and as far as I can tell there are no other options to set unless I want to work in a node based environment. Since two way communication is unavailable in our configuration this is impossible. One thing to note is that I _am_ able to tell the proxy to monitor remote hosts, so there is configuration data being passed and that portion is indeed functional. Does anyone have suggestions or ideas as to what the issue here may be? We are running both systems with CentOS 5 and Zabbix server / agent 1.6.1
-Sean
Comment