Tired of jumping between log files. Best way to piece together a cross-service timeline?

Posted by Waste_Grapefruit_339@reddit | linuxadmin | View on Reddit | 57 comments

I ran into this again today while debugging a mess involving several different services. The fix itself was a one-liner, but figuring out the "why" and "when" took forever.

My current workflow is basically opening four terminal tabs, grepping for timestamps or request IDs, and scrolling through less like a madman to piece the timeline together. It works fine when it's just two services, but once 4–5 services are logging at the same time, it becomes a nightmare to track the sequence of events.

How are you guys handling this?
Are you using specific CLI tools (maybe something better than tail -f on multiple files), or is everyone just dumping everything into ELK / Loki these days?

Curious to hear how you reconstruct the "truth" when things go sideways across the stack.