A filter for which subnets are added from discovery would be appreciated for this feature if it is added(and I hope it will be).

Reason for that is some controller type VM's can have several interfaces for communication with hardware devices in different subnets. Only the management interface may be required for monitoring.

I approve. Please add a filter to detect the IP in some subnets.

I want to auto-add all our VM, which have Zabbix-Agent2 install automatic. So in the Host prototypes of the template, I add a Interfaces Agent to connect them. But since some VM have more than one IP/VLAN, the discovery get any IP, which is not working for some.

Hi DevTeam,
I will add my +1 to this topic because seems interesting for some customers.
Thanks

i have the same issue, if anyone has a workround id love to know.. I'm new to zabbix, I wonder if i can put a filter on some discovery rule

same issue here
i hope one day a version get this feature

same issue here. would like to get this feature

We are facing the same problem with VMs that have multiple IP addresses assigned to them. This feature would be much appreciated.

A workaround on this is, in the VMWare Tools config, one can use the exclude-nics config to specific the nics that needs to be excluded. 

Proposal:

Taken into account that representation of vm in zabbix server is required only 1 correct interface/IP (the business reason for having multiple interfaces for a VM host prototype is still unknown ), we can do the following:

1. adding subset of vmware.vm.net.if.discovery subset to vmware.vm.discovery as "net_if" 

     "net_if": [
       {
         "ifip": ["127.0.0.1","::1"],
         "ifname": "aaa",
         "ifmac": "bbb",
         "ifconnected": true,
         "iftype": "VirtualVmxnet3",
         "ifbackingdevice": "VLAN(myLab)",
         "ifdvswitch_uuid": "ccc",
         "ifdvswitch_portgroup": "dvportgroup-111",
         "ifdvswitch_port": 123
       },
       {
         "ifip": [],
         "ifname": "aaa2",
         "ifmac": "bbb2",
         "ifconnected": false,
         "iftype": "VirtualVmxnet3",
         "ifbackingdevice": "VLAN(myLab2)",
         "ifdvswitch_uuid": "",
         "ifdvswitch_portgroup": "",
         "ifdvswitch_port": 0
       }
     ] 

1. create a new LLD macro with required IP via JSONPath. For example based on "ifbackingdevice":

   $.net_if[?(@.ifbackingdevice=="VLAN(myLab)")].ifip[0].first() 

1. supposed that user manually update the template of vm host prototype to use new LLD macro with correct IP

<MVekslers> The possible reason of a second interface is JMX or SNMP templates. It can be done with the same ip via second "host prototype" and "override" based on vmware tags (for example)

Hi Michael,
very good job!
The most classic "use case" it's to use the "right" IP address (i.e. management vlan) for simple ICMP Ping check or something similar.
Do you think this new improvement will be available on Zabbix 6.4.x releases or only on Zabbix 7.0?

Thanks so much

Available in:

• 7.0.0alpha7(master) 81d3b649756

Documentation (7.0) updated:

• Introduction > What's new in Zabbix 7.0.0
• Virtual machine monitoring:
  • Virtual machine discovery key fields (new "net_if" field for vmware.vm.discovery[]; new "ifip" field for vmware.vm.net.if.discovery[])
  • VMware monitoring setup example (new Advanced host interface configuration section)
• Discovery > Low-level discovery > Host prototypes (added link to Advanced host interface configuration section)

The problem that this modification to already existing machines adds a duplicate interface, which can not be removed because it is associated with existing items.

It's not entirely clear, this change just shows information about available IP addresses for the VMs and does not create additional interfaces

The last point of this instruction - changing the host prototype:
https://www.zabbix.com/documentation/7.0/en/manual/vm_monitoring/example#advanced-host-interface-configuration

This point will not replace, unfortunately, the interface entries but will add another interface.
Not being able to remove the previous one because of existing items. when we change the host prototype variable in interface , and later also when we restore

Wolvverine 

You could also try to add the "{#VM.IP}" macro to the VM discovery rule, instead of creating new macro "{#MYLAB.NET.IF}". This way, the value based on JSONPATH will replace the incoming value of the "{#VM.IP}" macro and you don't need to change the interface on the host prototype. In this case, the IP address can be replaced without errors. I tested this solution on a latest build from the master branch.

However, keep in mind:

1. If you replace as I described and there is no IP address according to the specified JSONPATH (the VM will not have this VLAN), then the interface will be changed to the unexpanded macro.
2. I haven't tested the behavior, what will happen if you already have an error about trying to delete the interface with attached items. Perhaps this solution will not help you, since you indicated that "and later also when we restore {#VM.IP}"