The first time, a cache entry expired before it was written. The second time, an audit trail showed a refund issued before the payment it refunded. Both times, two hosts disagreed about the time by a few hundred milliseconds.
Wall clocks are for humans
Use a monotonic clock to measure durations and timeouts. In Go, time.Since already does; in other languages you may need to ask for it by name.
start := time.Now()
doWork()
elapsed := time.Since(start) // monotonic, safe across NTP jumps
What every log line carries now
ts: the wall-clock time, in UTC, with milliseconds.hostandclock_offset_msfrom the last sync check.trace_id, so ordering comes from causality, not timestamps.
Order by cause, not by clock
When two events on different machines need an order, pass a version or sequence number along with the request. A timestamp from another host is a hint, never a fact.