Hi Team,
I created a service with an element which has alarms in dataminer cube, the service was created in UTC time(2025-07-01 09:00:53Z) but alarms created same time the service got created has UK time(Today 10:01:38) and not the same UTC time.
I'm trying to get the alarm history based on service start and end time and due to discrepancy(service using UTC time and Alarms recorded in UK time) in time, its not giving the right list of alarms.
Please let me know why this discrepancy is taking place and how can we fix that
Hi Hari,
Could you please let us know which DataMiner version you're currently using, and what type of storage is configured?
There was a known issue where alarm timestamps were displayed based on the local time of the client machine instead of the time defined in the DataMiner server. This has been resolved in the following versions:
Kind regards,
Hi Hari,
So the alarms' timestamps on the alarm console are correct.
As for the time properties of the services showing in UTC instead of reflecting the server-defined time zone, I recommend reporting this to TechSupport, so they can take a closer look.
Hi Catarina,
The dataminer version is 10.5.2.0.
But according to the link you provided, DMA is located in UK server, so the alarms in Cube are showing in UK time.
Whereas, Service creation is in UTC time.
https://docs.dataminer.services/release-notes/General/General_Main_Release_10.4/General_Main_Release_10.4.0_CU2.html?q=38899#dataminer-cube-search-for-alarms-would-list-alarms-with-timestamps-according-to-the-local-time-zone-of-the-client-computer-id-38899