Local log analysis guide
Syslog viewer for local system-log investigations
Search exported syslog, messages and journal text files in your browser. Keep hostnames, addresses and operational details on your device.
System logs are most useful as a timeline. A service failure may appear first as a kernel or network warning, then as a systemd restart, followed by repeated application errors.
Log Voyager preserves the original line order while giving you regex search, filters and bookmarks. It works with RFC 3164-style messages, RFC 5424-style text and journalctl output exported to a file.
Files and formats
/var/log/syslog · /var/log/messages · journalctl.txt · .log · .gz
Common investigation tasks
Build an incident timeline
Search the affected minute or service and bookmark events in chronological order.
Isolate one host
Filter the hostname when a central export contains messages from several systems.
Find priority messages
Search emerg, alert, crit, err or warning tokens used by the source.
Inspect service restarts
Locate systemd start, stop, exit-code and restart messages around the failure.
A practical workflow
- Export the log - Copy the relevant system file or redirect journalctl output to a local text file.
- Open it locally - Select the file or a rotated GZIP archive in Log Voyager.
- Search time, host and service - Start with the stable incident context before broad error keywords.
- Export the timeline - Save selected messages as a compact incident record.
Frequently asked questions
Can Log Voyager read journalctl directly?
It does not connect to systemd. Export journalctl output to a text file, then open that file locally.
Does it understand RFC 3164 and RFC 5424?
Both are text formats and can be displayed and searched. The viewer does not require one fixed syslog schema.
Can I open rotated .gz system logs?
Yes. GZIP logs can be selected and decompressed in the browser.