There´s a similar topic that other user explains that the parameter is not trendable and I´ve tried it at Aggregation rules too, without success.
I´d like to know, how could the Local Time be compared in order to Alarm some time span between servers and display what server has diferente time to be corrected.
This simple alarm will avoid many syncronization errors across the cluster, where the Administrator can correct the local time in case of eg. NTP failure.
Thanks in advance.
We are currently working on a BPA (Best Practices Analyser) to verify if all servers are running the same local time within a cluster, as you indeed mentioned this is crucial for our synchronization mechanism.
At this moment in time we already have a first iteration where we check if all servers are connected to the same NTP server. In your case this would give a warning if you NTP server would fail and probably what you are looking for?
This BPA is already validated by our QA department and good to use however we are going to improve it further as you describe to check the actual time on all the servers before we will add this to an official release (since it's allowed to connect to different NTP servers).
You can already get that BPA if you want by contacting firstname.lastname@example.org or by reaching out to your squad
More info on BPA:
If you do not have the latest version with the cube integration, we can provide a standalone application to run this BPA from DataMiner 9.6 version onward