live mode
Real-time log streaming
and remote tailing
Watch it happen. Not after the fact.
Point Logier at a streaming HTTP(S) endpoint and tail it in real time — filtered, searched, and sorted exactly the way you already work with a static file, on a service you can't SSH into.
while it streams
Filter and search while
the stream is running
Same filters as the static view
Toggle log levels and narrow by service exactly like you would on a file you've already opened — nothing about filtering changes because the source is live.
Search while it streams
Free-text search matches against message and service as new lines keep landing underneath.
Newest lines first
While connected, Logier sorts entries newest-first automatically, so what just happened is always at the top.
Snapshot to the editor
One click turns the current buffer into a regular file in Logier's editor, so you can keep exploring what already landed without staying connected.
how it connects
Connecting to an
authenticated endpoint
URL
Any HTTP or HTTPS endpoint whose response body streams text.
Headers
Optional JSON block for an Authorization bearer token or other auth headers.
Buffer size
How many lines to keep in memory at once — 5,000 by default, yours to adjust.
where this lives
A live stream is just another tab
Once connected, everything you already know how to do with a file works the same way — the source is the only thing that changed.
Explorer
Cloud
- 1
The stream opens as a tab with a live indicator, alongside any static files you already have open.
- 2
Live Mode lives in the nav rail. Give it a URL, optional auth headers, and a buffer size.
- 3
Filters and search apply to the stream as it arrives — no reconnect, no re-running a pipeline.
- 4
The timeline builds itself in real time, so you watch the shape of an incident form.
versus the terminal
Live Mode vs. tail -f over SSH
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 managed platform that only exposes logs over an authenticated HTTP endpoint, or on a customer's infrastructure that will hand you a URL and nothing else.
| Logier Live Mode | tail -f over SSH | |
|---|---|---|
| Needs shell access | No — just a reachable URL | Yes, SSH or kubectl exec |
| Log levels | Parsed and filterable while streaming | Plain text; grep it yourself |
| Filter mid-stream | Toggle levels and services, no reconnect | Re-run the pipeline |
| Timeline and clustering | Live, as lines arrive | Not available |
| Keeping what you saw | Snapshot the buffer to the editor | Redirect to a file up front, or lose it |
| Authentication | Custom headers, incl. bearer tokens | Whatever SSH gives you |
what to point it at
Endpoints that work
Anything whose response body is a stream of text over HTTP(S). A few shapes that come up often:
Kubernetes log proxy
A follow endpoint on the API server, or any sidecar that re-exposes pod logs over HTTP.
https://k8s.internal/api/v1/.../log?follow=true
Managed platform log stream
Most hosting platforms expose a live log endpoint with a bearer token — paste the token into the headers field.
{ "Authorization": "Bearer <token>" }CI job output
A running build's live log URL, so you can filter a noisy pipeline while it's still going.
https://ci.internal/jobs/8412/output.stream
Your own bridge
Anything that turns a local file into an HTTP stream works — including a few lines of your own.
tail -f app.log | your-http-bridge --port 8080
faq
Common questions
keep reading
Working with a live stream
Automatic format detection
Streamed lines run through the same parser registry as a file on disk, so levels and timestamps resolve live.
Timeline view
Watch the shape of an incident form in real time rather than reconstructing it afterwards.
Anomaly detection
Frequency spikes and new error signatures get flagged as they appear in the stream.
AI root cause analysis
Snapshot the buffer to the editor, then ask what caused the burst you just watched land.
A GUI alternative to tail -f
Command-by-command: what you'd type in a shell, and what Live Mode does instead.
Logier vs. lnav
lnav's follow mode survives log rotation and works over SSH. An honest comparison.
See it the moment it happens.
Point Live Mode at any streaming endpoint you're already authorized to reach — no separate agent to install.