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.
Great use case Henrique, thanks for sharing. Let us take a look at that, because there should be a way to make this possible.
In the meanwhile, I checked and there is a 'Last Time Sync' metric also that can be monitored. Maybe that can help you to get a heads up for cases where NTP seems to be failing?
Hello Ben, Thanks for answearing.
It could be, better would, if the metric could be calculated internally by the DMS process.
What if, in the case the server is not using NTP? In our case, NTP is setup at vSphere host, I would suggest to use the local computer time to compute difference.
Let´s see what comes!
Best regards.
*Local Time is a parameter in the Microsoft Platform driver*