I have a Hyper-V server which is monitored in PRTG, say HSERVER1, and its VMs are all monitored as well, say VM1, VM2.

I have set the dependency at the device level for VM1 and VM2 to be dependent on the Hyper-V service on HSERVER1.

I then paused HSERVER1 for maintenance and the sensors for it all went blue as did the ones for VM1 and VM2 - looks good so far. Then I shut down just the machines VM1 and VM2.

After a short while the various sensors of VM1 and VM2 started to wake up and went red - the DNS being used by the separate PRTG server is actually the two VMs (yes I know, not the best idea).

Why did the sensors of VM1 and VM2 start getting alerted? They should be paused as the Hyper-V is still down from the manual pause of the device.

Article Comments

Hi,

Are you running 19.3.52.2830 already? It fixes a multitude of dependency issues and this might be one of them. Please let me know if the issue persists after an update. Note that pausing an object another object depends upon, the dependency will not go into effect:

https://helpdesk.paessler.com/en/support/solutions/articles/76000063274-why-will-dependent-objects-not-go-into-paused-status-automatically-when-i-pause-the-master-object

PRTGapi | Feature Requests | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team


Sep, 2019 - Permalink

I'm on 19.3.52.3478+


Sep, 2019 - Permalink