Scott Laird<p>Huh. Now that I have <a href="https://hachyderm.io/tags/otel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>otel</span></a> traces on a bunch of things at home, it's pretty clear that my clocks aren't in sync on every system. They're maybe 1ms off, but it's enough that supposedly-nested trace spans aren't quite nested right.</p><p>Which is annoying since I have two local GPS <a href="https://hachyderm.io/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NTP</span></a> receivers.</p><p>The two "bad" machines were using <a href="https://hachyderm.io/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>systemd</span></a>-timesyncd to talk to Ubuntu's pool clocks instead of the local clocks. The "good" machines are using <a href="https://hachyderm.io/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chrony</span></a> and claim that they're ~2 us off of GPS time.</p><p>Now I'm curious -- is this a problem with network latency and Ubuntu's pool, or is that just as good as timesyncd gets?</p>