We configure zabbix-proxy on pfSense firewalls in multiple remote Data Centres.
We install zabbix-agent on Windows/Linux VM behind those firewalls.
We configure those zabbix-proxies and zabbix-agents on our zabbix-server in remote Data Centres.
When we configure Web Monitoring, we want to the status of the URL as it appears from the zabbix-server (how it used to work some time ago), not from the zabbix-proxy (how it works now).
Monitoring from zabbix-server would give us a better idea if the public can see the website over the WAN, rather than just the zabbix-proxy being able to see it over the LAN.
If we create the Web Monitoring on the zabbix-server we lose ability to use any agent level features, such as actions specific to host or host-group or variables such as {HOSTNAME}.
Is there any way currently or planned for the future to be able to say "Use zabbix-server to perform Web Monitor" and/or "Use zabbix-proxy to perform Web Monitor" and/or "Use zabbix-agent to perform Web Monitor" ? This would give us the flexibility we need.
We install zabbix-agent on Windows/Linux VM behind those firewalls.
We configure those zabbix-proxies and zabbix-agents on our zabbix-server in remote Data Centres.
When we configure Web Monitoring, we want to the status of the URL as it appears from the zabbix-server (how it used to work some time ago), not from the zabbix-proxy (how it works now).
Monitoring from zabbix-server would give us a better idea if the public can see the website over the WAN, rather than just the zabbix-proxy being able to see it over the LAN.
If we create the Web Monitoring on the zabbix-server we lose ability to use any agent level features, such as actions specific to host or host-group or variables such as {HOSTNAME}.
Is there any way currently or planned for the future to be able to say "Use zabbix-server to perform Web Monitor" and/or "Use zabbix-proxy to perform Web Monitor" and/or "Use zabbix-agent to perform Web Monitor" ? This would give us the flexibility we need.