live tailing

A GUI alternative to
tail -f for remote logs

Tailing works when you have a shell on the box. Increasingly you don't — the service runs in a container you can't exec into, on a platform that only exposes logs over an authenticated HTTP endpoint, or on infrastructure that hands you a URL and nothing else.

side by side

What you'd type,
and what you'd click

The first few rows have a perfectly good CLI answer. The bottom half is where a pipeline runs out.

TaskShellLogier Live Mode
Follow a log as it's writtentail -f app.logConnect Live Mode to a streaming endpoint
Follow through log rotationtail -F app.logThe stream is the source; rotation is the server's problem
Only show errorstail -f app.log | grep -i errorToggle the error level — no reconnect
Change what you're filteringCtrl-C, edit the pipeline, run it againToggle a different level; the buffer is still there
See how often it's happeningNot availableThe timeline builds live as entries arrive
Distinguish new errors from repeatsNot availableClustering counts repeats; new signatures are flagged
Keep what you saw after stoppingtail -f app.log | tee capture.logSnapshot the buffer to the editor
Authenticate to a protected sourceWhatever SSH gives youCustom request headers, including bearer tokens

when to just use tail

tail -f is still right
more often than not

If you have a shell on the machine and a path to the file, nothing here beats typing eleven characters. It's already installed, it composes with every other tool you have, and it works over SSH where a desktop application simply cannot follow. The case for a GUI starts at the point where you can't get that shell — or where you need to change what you're filtering without losing everything that already scrolled past.

faq

Common questions

keep reading

Related reading

Tail what you can't SSH into.

Point Live Mode at any streaming endpoint you're already authorized to reach.