VMware Guest: VM is not running - little question

[Bitz0r]

I have the standard template with the expression:

last(/VMNAME/vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}],#3) <> 2

Unfortunately, an event is generated very often.
Is there any way to “fine-tune” this more? I believe that as soon as a VM is migrated via vMotion or something else, the trigger smoke is triggered.

[Zaaappe]

I have the same behavior, I tought some vms were rebooted but it was just vmotion. But I think its because there's no state in "vmware.vm.state" for vmotion.
I think the best (not the ideal) would be to install the zabbix agent and then disabled the trigger for VM is not running.

[cyber]

I have the standard template with the expression:

last(/VMNAME/vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}],#3) <> 2

Unfortunately, an event is generated very often.
Is there any way to “fine-tune” this more? I believe that as soon as a VM is migrated via vMotion or something else, the trigger smoke is triggered.

That trigger is edited by someone and completely screwed up .. "last(/host/item,#3)..." means 3rd value from the end... So it triggers 3 minutes after something has happened...
Original should be

last(/VMware Guest/vmware.vm.state[{$VMWARE.URL},{$VMWARE.VM.UUID}]) <> 2

there is no state for vmotion... there are

I guess during host migration you get not running from one host and running fro another? I am not much of vmware specialist..