VMware discovery get wrong VM.IP

[dcournoyer]

I'm using Zabbix 6.2.0rc1 with the latest 6.2.0 VMware Template.

The issue, many of our virtual machines get multiple IP addresses. When the discover start, it only get the first IP address it gets from vCenter JSON, and assign it to {#VM.IP} (I can't find where that is done).

After looking at what vCenter is sending, I see that all the IPs are send correctly.

I'd like to put a filter on the VM.IP detection so only certain subnet gets find, and not the first one.

I saw the host prototype where the assignment is done under the template "VMware", "Discover VMware VMs" discovery rules, and "VMware: {#VM.NAME}" host prototype.

What can I change so the IP is detected correctly?

[dcournoyer]

Anyone have any hint for me?

[vladimir_lv]

Hi!
As far as I understand this separate feature request is still not added. Please check:

https://support.zabbix.com/browse/ZBXNEXT-7754

[dcournoyer]

Hi!
As far as I understand this separate feature request is still not added. Please check:
https://support.zabbix.com/browse/ZBXNEXT-7754

Oh thank you. So I assume it's nothing that can be change in templates but really in the code...

[archnem]

6.0.6 LTS here and I agree this feature would be very welcome. Just came across the same problem as some of our monitored VM's have several interfaces and IP addresses. It would be very useful if it was possible to filter the subnets that are populated, or some other way define which of the discovered IP's are used. Voted on the mentioned feature request and added a comment as well about subnet filtering.

Anyone else who is interested in this topic should vote for the feature request to help get attention to this requirement.