Synchronizing the clocks in a testing or production environment

To prevent unexpected results from a solution, ensure that the clocks on your Decision Server Insights servers and your event sources are synchronized within the required tolerance of the solution.

About this task

The clocks in all the servers in the cluster, and the clocks that are the source of the event timestamps, must be synchronized so that their times are off by less than the shortest time frame that is used by the solution.

For example, suppose the shortest time frame that a solution uses is 30 seconds:

when my event has occurred 30 seconds ago ...

In this example, all the clocks in your network must be much more accurate than within 30 seconds. If the clocks are off by 15 seconds, any references to time can be off by +/- 15 seconds. If the clocks are off by 1 minute, the effect is that the reference to 30 seconds could include events that occurred up to 1 minute and 30 seconds ago.

Procedure

Ensure that all of the servers run on a standard time by using a public time server or other global timing application.
Similarly, ensure that the sources of your events are synchronized and verify them against your servers.