Set up Zabbix (3.0) to monitor a couple of agentless web sites - using net.tcp.service[https] and a small web scenario. As all sites are agentless, I simply left the default entry pointing to127.0.0.1 (after reading a while in this forum). The web scenario worked immediately, but it took me a couple of hours to find out why net.tcp.service die NOT work:
Web scenario connected to {HOST.HOST} using the DNS host name as requested.
net.tcp.service[https] however tried to connect to the agent interface 127.0.0.1 - which I really did not expect. As soon as I enter the host name for the agent interface, everything is fine (even though there is no agent at all - but this IP address is used for the tests).
Why is this? This thread: https://www.zabbix.com/forum/zabbix-...https-services is claming that net.tcp.service is working with 127.0.0.1 (most likely meaning: "with any IP address") for the agent interface, and this would be intuitive as well.
Did I miss anything?
Web scenario connected to {HOST.HOST} using the DNS host name as requested.
net.tcp.service[https] however tried to connect to the agent interface 127.0.0.1 - which I really did not expect. As soon as I enter the host name for the agent interface, everything is fine (even though there is no agent at all - but this IP address is used for the tests).
Why is this? This thread: https://www.zabbix.com/forum/zabbix-...https-services is claming that net.tcp.service is working with 127.0.0.1 (most likely meaning: "with any IP address") for the agent interface, and this would be intuitive as well.
Did I miss anything?