We just noticed this after upgrading to 10.3.7. Active Alarms are in US Eastern Standard Time, which is the time that our servers are on while the history tab alarms will be displayed in US Pacific Standard Time, which is what the client devices which host Cube are on. One of our clusters is on an older version of DataMiner and this issue is not present there.
Is there anything we need to do to make the entire alarm console consistently match server time?
Hello Ryan,
Please check Frequently asked questions about general configuration | DataMiner Docs
you will be redirected to "Time Server" and right after "Time Client"
please, follow the instructions, normally it should work.
Please, inform us the results.
Hi Ryan,
There was an issue with the timing of the alarms in 10.3.7CU0 but it has been resolved in 10.3.8CU0.