Hi, we use PRTG in several countries spread over the world and therefore in different time zones. The timely display of the sensors is based on UTC + time zone from my account settings. We would rather prefer that a probe has it's own time zone to see local time and not my time. Is there a way to accomplish this?

Greetings, Mike

Article Comments

this is not possible, sorry.

Only solution would be to log in with another user account that uses the timezone the remote probe is in


Jul, 2011 - Permalink

thanks for reply. Is it planed in further versions?


Jul, 2011 - Permalink

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:

  1. On weekdays 9-to-5
  2. 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.


Oct, 2011 - Permalink

I agree, have sensors show graph in a custom timezone would be very helpful.


Jul, 2022 - Permalink