Logging & Journald

Stop paging through endless logs when you only care about the last ten seconds

🧩 The Challenge

Trying to catch a transient error in a high-traffic service is a nightmare when journalctl defaults to dumping the last thousand lines of junk you don’t need. I’ve wasted way too much time scrolling past ancient events while the actual crash just happened.

💡 The Fix

Just use the follow mode with a specific time filter so you only see exactly what’s hitting the buffer right now. It saves your eyes from scanning history that already logged hours ago.

journalctl -u your-service-name.service -f --since "10 seconds ago"

⚙️ Why It Works

Passing that specific time window forces the pager to ignore the mountain of existing logs and start its stream immediately at your current timestamp. And since you’re using -f, it keeps the terminal open to show you the live chaos as it unfolds.

🚀 Pro-Tip: Combine this with -o cat if you’re sick of the timestamps clogging up your view while watching a live tail.

Linux Tips & Tricks | © ngelinux.com | 10/4/2026