We are using vRanger to back up our VMs. During that time, our WMI and Ping sensors trigger and generate spurious alert messages. This is probably because vRanger takes a snapshot of the running VM and backs that up. During the snapshot we suspect services are briefly interrupted.
While I completely respect that this is exactly the sort of thing that PRTG is supposed to detect, it's generating a lot of spurious errors that are causing our users to miss 'real' errors that are hidden amongst all the spurious ones.
My manager would prefer that we do not use a scanning schedule that stops scanning the various machines overnight, in case there is a real error on the affected systems. Is there another way I can deal with this?
Thanks.
Dear Matthew,
I would recommend working with two triggers and therefore two notifications here. One trigger for the day, and the other trigger with a much longer latency for the night. And then use schedules on the notifications, so that the notification for the "night trigger" is only active during night hours, and the other one vice versa. Would that be an option?
best regards.
Jan, 2013 - Permalink