That all sounds very normal to me, and it's what I'd expect most people do. The bit that surprised me is more likely due to my background being mostly Ruby/sim

That all sounds very normal to me, and it's what I'd expect most people do. The bit that surprised me is more likely due to my background being mostly Ruby/similar based, which is around debugging highly concurrent apps. Our app spins up goroutines all the time. One request will fan out to a number of concurrent threads, doing things like hydrating responses from Slack to syncing issue tracker tickets. With your STDOUT logs, that's so difficult to understand as it's all interwoven. And picturing all the threads and how they interact is fairly difficult. I think that's why this was such a "ah-ha!" moment for us. Suddenly we could find the "error" log in our terminal, then click the trace URL and see everything in context. That's probably the key difference to our past experience, that the app we're working with is so concurrent.