Why doesn't Zabbix agent state change after proxy is disabled?

Question

Zabbix

Good afternoon, dear experts,
I can’t understand why Zabbix does not signal that the proxy is disabled.

What is:
1) on the one hand, a virtual machine on VMware - Debian-10.8.0 (zabbix server, agent, postgres, nginx)
2) on the other hand, a virtual machine on Hyper-V - Debian-10.8.0 (zabbix proxy, agent)
All components are raised in docker containers using yml files and the docker-compose up command.

The proxy is configured in Zabbix Frontend and works fine:


When a new host is connected (I want to monitor the proxy itself) and the docker container with the agent is installed in the Interface ip column, the system starts signaling the availability of the agent:


Problem:
if you disable the Hyper-V virtual machine hostingboth docker containers are proxy and agent , the state of the latter does not change - the system sees it as available and does not signal that the proxy and all devices behind it are unavailable. If the proxy is alive, but the agent is not, everything works out according to the given logic.

Templates, Items and Triggers did not change. The version of the entire park of Zabbix components is 5.4.2.

Help me please.

Answer 1

If I understand the logic of zabbix work correctly, then the lack of communication with the zabbix proxy is not the same as a problem on the node / nodes on the proxy server itself or nodes behind them.
To receive a notification about the loss of connection with the proxy server, you need to configure an active availability check on the Zabbix server itself, as it seems to me.