Hi,
it's me again. I just want to add this to emerge that time-zone support would really be highly appreciated:
We are using PRTG to monitor a lot of devices spread over the world. That means that many remote probes are in different time-zones than the core server. Now we wanted to plan a bandwidth monitoring of all of them, but we are not interested in a 24/7 monitoring. So the basic idea was to monitor:
- On weekdays 9-to-5
- On weekends 0-to-12
based on the time-zone the remote probe is located. We ran some test and had to find out that the schedule of the sensor (e.g. weekdays 9-to-5) is based on the time-zone of the core server (in our case currently UTC+2) and not on the time-zone of the device where the remote probe is installed.
For example: the sensor on a device located in Mexico resumes at 9 (UTC+2) - that's 2 o'clock in Mexico! (far away from working hours)
So, in a nutshell: Scheduling remote probes in different time-zones is basically possible but monitors other time periods as expected and is therefore not useful for us.
Add comment