Multiple client creation after moving between nodes

[ucakmakci]

Hello,

I'm using your Hyper-V template script and it works nice. Thanks for this. On the other hand, I have a problem with hyper-v server with cluster structure. When a virtual machine moved-migrated to another hyper-v node on it create an another Host on Hyperv VM hostgroup.

For example This list of the host group on first HyperV Node; VirtualMachineABC_Node1

The list of the host group when moved-migrated to another node; VirtualMachineABC_Node1 (This one stays and values became passive ) VirtualMachineABC_Node2 (Creates another host for older VM)

I hope i could explain.

Thanks anyway.

[ameiji]

Hello, this discovery logic is intentional and was introduced in 1d2aa5c44051cfcb214939f3b64ad8cde74f1e7c As you have noticed the guest name includes node name as well, which leads to duplicate zabbix host entries - one is active and other becomes passive. But without this logic, when a Hyper-V migration occurs, zabbix host entry for this guest becomes passive and this guest cannot be discovered anymore, which we don't want. There might be a better way to deal with migrations and discovery logic. I may look into that in future, but can't promise I'll do ;) If you got any suggestions, please do share.

[a-schild]

Perhaps remove no longer detected guests after X hours/days? (Can autodiscover remove hosts?)

[a-schild]

Hello, I have received ownership of this repository. Is this issue still valid, and if yes, do you have a solution for it, or more analysis?

If no answer is received by end of march 2024 I will close this issue

[NGC2068]

Hello, can you hold off a bit, I'm testing your monitoring template in the meantime?