When working within the DataMiner Dashboard app the date & time matches the client configuration. Therefore, resulting reports or CSV exports will match the client date and time.
On the other hand, when working with Cube, resulting reports match the server date and time.
We understand that the above different behaviors are are driven by:
- Cube sits on top of the operating system and is able to retrieve the time zone of the server
- Web apps (Dashboards, Monitoring & Control, etc..) are not aware of the server time zone and default to the client application settings, instead
Based on above, we are left with the following questions:
- Is there a way to, optionally, change the described behavior and have the dashboards use the server date & time if preferred?
- If not, would a new software feature be required to implement this use case?
Thank you,
That is indeed the default behavior. It is possible to override this default behavior, by configuring what timezone you want to use in all client applications. This can be done per user in the clientsettings.json:
1. Open the file ClientSettings.json in the folder C:\Skyline DataMiner\Users.
2. Set the setting commonServer.ui.DefaultTimeZone to the time zone you want.
For example:
{
"Name": "commonServer.ui.DefaultTimeZone",
"Value": "Pacific Standard Time;-480;(UTC-08:00) Pacific Time (US & Canada);Pacific Standard Time;Pacific Daylight Time;[01:01:0001;12:31:2006;60;[0;02:00:00;4;1;0;];[0;02:00:00;10;5;0;];][01:01:2007;12:31:9999;60;[0;02:00:00;3;2;0;];[0;02:00:00;11;1;0;];];",
"VersionNumber": 0,
"Mode": 0,
"InVisible": false
}
To retrieve the correct format for the time zone, the TimeZoneInfo.ToSerializedString method can be used. See https://docs.microsoft.com/en-us/dotnet/api/system.timezoneinfo.toserializedstring.
3. Save and close the file.