Hi from a boat full of gizmos (and their log files)
Hi everyone, I'm Thomas! I live on a boat (mostly along the US east coast, and every year we run from the Florida hurricane season), and that boat is full of gizmos: a Cerbo GX, an NVIDIA Jetson, eight Garmin chartplotters, eleven UniFi cameras and of course a Mac mini.
So naturally I ended up writing software for all of it... first a boat tracker that tells friends when we leave or arrive at a marina, then an app that shows my UniFi cameras on the Garmin screens (which Garmin doesn't support out of the box, or at all, really), and a few Mac apps along the way, like PanoPaper, which lets me view those cameras as a live video wallpaper on my Mac.
Now... every one of those things writes its own logs on its own device, and after one too many evenings of SSH'ing into three boxes at once I built LogRaker, a native Mac app that tails all of them in one window, side by side and lined up by time. It's launching here on Product Hunt later this month.
I'm new around here (more active on HN), so I'd love it if you'd check out the app before we launch, and tell me how you keep an eye on your own logs (or what's missing and you'd want to see!)
Happy to answer any questions!
- Thomas.
Replies
Great boat setup. Our logs live on users' phones, so the habit is different: the app writes a plain text log file on the device in every build, and a user can share it from Settings when something goes wrong. Each line is written as a plain statement of what happened, every silent give up gets its own line, and every tap is logged by a stable English control name rather than a translated label. Lyrics, passwords and one time codes must never go into it. On the emulator it's logcat beside screenshots. One question about lining things up by time: what does LogRaker do when two boxes disagree about the clock? We had a phone whose idea of UTC ran nine hours ahead, and anything ordered by its timestamps would have been nonsense.
Hi @gbasovv thanks! I like the "every silent give up gets its own line" rule, I wish half the gizmos on this boat did that...
So, clock skew was one of the first things that bit me, since the Cerbo GX and the Jetson never quite agree with my Mac mini (or with each other, really). So every time LogRaker connects to a box over SSH, it asks for that box's clock and time zone a few times in a row, keeps the answer with the shortest round trip (same trick NTP uses), and moves that Source's timestamps onto the Mac's clock. If a log line doesn't say what time zone it's in, it gets read in the server's time zone, so a phone nine hours off would've been caught one way or the other.
Of course, you can't SSH into Firebase or CloudWatch etc, so for those you line things up by hand: right-click a line in the log whose clock you think is right and pick 'Set Ref Time', then right-click the same event in the other log and pick 'Align to Ref Time', and the whole Source shifts over. A little badge in the pane header shows the offset afterwards.
Happy to answer any other questions!
@gbasovv I made it into a blog post with addle. information:
https://lograker.app/blog/when-two-clocks-disagree
Thanks for the inspiration ;)