@victor said in Critical Paths:
Hi!
It's not possible to specify such relation manually. Anyway, it is layer 2 connectivity issue, not layer 3, as both nodes (physical host and VM) are in same subnet, so 192.168.1.10 is not involved in the routing process, but acting as Ethernet bridge. I will add a feature request for including layer 2 topology into event correlation process.
As a workaround, you can check status of the host node in the script in event processing policy, but this may not work as expected if VM polled first (so server don't know that host is already down).
Best regards,
Victor
Thanks - I might give that a go as the event I am using waits for 5 minutes before emailing so the server must be down at the same time as the VM.
