Currently when users deploy new installation of Zabbix there is one host already - Zabbix server with template "Zabbix server" linked to it. This is good, as internal metrics are automatically monitored.
Sadly this is not the case with proxies. User needs to remember that after creating a proxy one must also got to Configuration -> Hosts and also create another host, monitored by this proxy and link template "Zabbix proxy" to it.
I propose automating this task by creating the internal metrics host with the same name automatically. Or this could be optional when creating proxy. We might also need a choice of which template should be assigned, as the name might differ.
Another way to do it is to just reuse the same host already existing in DB, it's identified by the status parameter:
0, HOST_STATUS_MONITORED - Host is monitored
1, HOST_STATUS_NOT_MONITORED - Host is not monitored
3, HOST_STATUS_TEMPLATE - The record is template
5, HOST_STATUS_PROXY_ACTIVE - The record is active proxy
6, HOST_STATUS_PROXY_PASSIVE - The record is passive proxy
Currently many users suffer from a situation where Zabbix is having major problems because proxies are overloaded/misconfigured, but do not know about it because they forgot to monitor it's internal stats.