Rudder

Well, there is technically very little that can be done, and even less if we want to implement an asynchronous reporting system, where the node could send reports only 1 time by day for ex - we will need to believe the timestamp it set.

So the question is more "how can we help a user (especially a new one) to be aware of the importance of time synchronisation between server and node, especially if we are receiving message in the past or in the future".

=> adapt the compliance reports header message for that?
=> had "node time" or similar adjective in technical log table header and other relevant places.

It is a documented prerequisite for Rudder that all nodes must have correctly configured clocks, and preferably a tight time synchronization using ntp. This bug therefore only concerns a case that will never occur.