Was there not a third option: Calling the journalctl CLI as a child process and consume the parsed logs from the standard output? This might have avoided both the requirement to use CGO and also to write a custom parser. But I guess I am missing something.
This was the first thought that occurred to me too when I saw this post.
But I'm also thinking about it as a product manager based on my tech experience. Looking at what people like in mugs, creating templates to exactly size the mugs to people's preferences, creating re-usable molds to put repeatable components together, and taking detailed notes on exactly what I am doing in-studio to create a repeatable, reliable process to create a product that will sell.
It is going poorly so far, but each iteration gets better, so hopefully I have everything down before I end up with 100+ unsellable mugs in my kitchen.