We have requirement of setting SDT to some servers which are in different time zones. The current time zone setting is portal-wide, so it is not based on group of devices as we require.
This would be a very welcome feature for any companies that have sites in multiple timezones, suggest LM should look into this and implement this feature on priority.
ProfessorAgree. The current single time zone makes managing SDT across time zones very difficult, especially for us enterprise customers with large IT estates.
ProfessorThis has been asked many times, including by me, but we so far have no indication it is on the roadmap and if so, where. It is an annoying gap, but arguably could be complicated to do properly. But really, if each device has a timezone and you need to display data together aligned to the same actual time, it is not hard to normalize to UTC, then render graphs in the user default timezone or a specific timezone. Hopefully this gets attention soon...
Mark
Professor@Sarah Terry Hi Sarah, any update on this please?
On 6/21/2017 at 6:06 PM, Shivaprakash Y said:We have requirement of setting SDT to some servers which are in different time zones. The current time zone setting is portal-wide, so it is not based on group of devices as we require.
This would be a very welcome feature for any companies that have sites in multiple timezones, suggest LM should look into this and implement this feature on priority.
Any updates on this ? This is an important feature which everyone is looking for, kindly look into this on high priority.
+1 on this.
Perhaps the time zone could be assigned to the SDT instead as this would be a cross functional change in how SDT's are set up on devices and services. Just add a box to select the time zone you are inputting your SDT for. This would also allow for instance / datasource SDT's to be "timezoned" too.
Our biggest pain point with this is having to address recurring SDT's up to 4 times a year, daylight savings +/- and british summer time +/-
