Hi all,
I am looking into using the VMWare monitoring on our 1000+ host network, but it seems to be problamatic when used with agent auto-registration.
When new machines are deployed, the VMWare templates pick them up and add the hosts correctly, once the base system is installed and the zabbix agent runs for the first time, the auto-registration I have configured adds a new host.
But the agent only knows the configured host name of the virtual machine, not the UUID of the VMWare 'job'. This means almost all of my attempts end in machines being duplicated. Once for the VMWare discovery and once for agent auto-registration.
What's more, I can't edit anything on the auto-registered host as I always get the error "Host with the same visible name "<name>" already exists."
Am I missing some part of the configuration, or is the monitoring meant to be an either-or situation and the two types of monitoring cannot be merged?
Thanks in advance.
I am looking into using the VMWare monitoring on our 1000+ host network, but it seems to be problamatic when used with agent auto-registration.
When new machines are deployed, the VMWare templates pick them up and add the hosts correctly, once the base system is installed and the zabbix agent runs for the first time, the auto-registration I have configured adds a new host.
But the agent only knows the configured host name of the virtual machine, not the UUID of the VMWare 'job'. This means almost all of my attempts end in machines being duplicated. Once for the VMWare discovery and once for agent auto-registration.
What's more, I can't edit anything on the auto-registered host as I always get the error "Host with the same visible name "<name>" already exists."
Am I missing some part of the configuration, or is the monitoring meant to be an either-or situation and the two types of monitoring cannot be merged?
Thanks in advance.
Comment