← Blog

Date:Sun, 15 Nov 2026 From:Thomas Gumz <thomas@lograker.app> To:You Subject:

When Two Clocks Disagree

Someone on Product Hunt asked me the other day what LogRaker does when two boxes disagree about the clock, since they once had a phone whose idea of UTC ran nine hours ahead, and anything ordered by its timestamps would’ve been nonsense. Good question, and one that bit me pretty early on, so here’s the long answer.

Nobody on this boat agrees what time it is

The Cerbo GX, the NVIDIA Jetson and my Mac mini never quite agree on the time (or with each other, really). Usually it’s only a second here and a few seconds there, which doesn’t sound like much until you’re trying to figure out what happened first. The whole point of LogRaker for me was to pick a moment in the Cerbo GX log and see what Firebase logged around that time, but with the clocks a few seconds apart, a merged view happily shows you the reaction before the thing that caused it… not exactly helpful.

And then there are time zones. Plenty of log lines just say 14:32:07 and leave it up to you to guess which 14:32 they mean, and a box set to UTC is hours off from a Mac on Eastern time before its clock has drifted a single second.

Over SSH, LogRaker just deals with it

So every time LogRaker connects to a server over SSH, it asks that machine for its clock and time zone five times in a row and keeps the answer with the shortest round trip (same trick NTP uses, since the quickest round trip is the one least thrown off by Wi-Fi or a VPN). Then it moves that Source’s timestamps onto the Mac’s clock, and if a log line doesn’t say what time zone it’s in, it gets read in the server’s time zone instead of the Mac’s.

You don’t have to lift a finger for any of this. Select the Source in the sidebar and its detail pane shows the server’s time zone and, once the two clocks are a second or more apart, the offset too. Anything smaller still gets corrected, it just isn’t shown, since at that point it’s mostly network jitter and you’d see a different number every time you looked.

… and then there’s the cloud

Of course, you can’t SSH into Firebase, or Amazon CloudWatch, or any of the other cloud services, and ask them what time it is, and the same goes for a log file someone sends you from their phone. So for those you line things up by hand, and it only takes two right-clicks. In the log whose clock you trust, right-click a line and pick ‘Set Ref Time’, then find the same event in the other log, right-click it and pick ‘Align to Ref Time’, and that whole Source shifts over so the two lines land on the same moment.

While you go hunting for the matching line, the status bar under every table reminds you what you pinned (and if you pinned the wrong one, ‘Clear Ref Time’ gets rid of it). The correction belongs to the Source, so every Stream from it moves together, it sticks around between launches, and if you aligned to the wrong line, Undo takes it back. Afterwards a little clock badge in the pane header shows the offset and the Stream it was lined up with, and ‘Clear Time Alignment’ removes it again if you ever want to.

Lining up the panes

Getting the clocks to agree is really just the setup, though. The part I actually use every day is ‘Sync to selected Time’. On my desk that’s a Layout with the Cerbo GX’s Boat Tracker log on top and the Firebase backend log below, and when something looks off in one of them, I right-click that line and pick ‘Sync to selected Time’ (or just double-click it). Every other pane jumps to its own line closest to that moment and selects it, and since it goes by the corrected timestamps, the Firebase pane lands on what actually happened at that time instead of somewhere a few seconds off.

The panes also stop scrolling, so the moment doesn’t run away from you while new lines keep pouring in behind the scenes. A small marker in the first column shows where that moment sits in each log, and a “Synced @” pill in the pane’s bar shows the time. Scrolled off somewhere? Click the time in the pill to jump back, or the x to drop the sync and let the panes follow the live output again.

And if right-clicking gets old, ‘Lock siblings to this pane’ makes one pane drive the others, so just clicking or arrowing through its lines drags every other pane along with it, which is pretty much what I wanted from day one, stepping through a whole sequence of events across the boat and the server, one line at a time.

The docs have all the details and gotchas on aligning clocks and the bar above each pane.

So, if your logs are scattered over more than one machine and those machines can’t agree on what time it is, give LogRaker a try. It might save you a lot of squinting at timestamps!

Thanks for reading!