Does anyone know how the behavior for web checks have changed in 2.2?
I noticed that web checks are located under the host configuration versus there own heading in our 1.8 installation. Specifically I'd like to know if that means when we specify a URL now if the host header can be different than the host name. When specifying a host header that differs from the server name, will Zabbix send a request to the server that the web check is defined to specifically or will it simply check against the URL like it does in 1.8
This is a weakness for us in 1.8 as we need the ability to monitor several servers behind a load balancer using the same URL. I was able to work around it by defining a curl check in the zabbix config file on the server, but all checks I have defined show up under the zabbix server and not the server we are actually checking against. It works, but it would be better to have the checks show up under the correct server so we can send alerts to only the correct people if it is tripped.
~Phil
I noticed that web checks are located under the host configuration versus there own heading in our 1.8 installation. Specifically I'd like to know if that means when we specify a URL now if the host header can be different than the host name. When specifying a host header that differs from the server name, will Zabbix send a request to the server that the web check is defined to specifically or will it simply check against the URL like it does in 1.8
This is a weakness for us in 1.8 as we need the ability to monitor several servers behind a load balancer using the same URL. I was able to work around it by defining a curl check in the zabbix config file on the server, but all checks I have defined show up under the zabbix server and not the server we are actually checking against. It works, but it would be better to have the checks show up under the correct server so we can send alerts to only the correct people if it is tripped.
~Phil
Comment