pickfit

BrowseData & database tools

lnav

A terminal log file viewer that merges, indexes, filters and queries log files by time, with SQLite-based analysis.

Tested on Linux

Use it

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. download static linux-musl-x86_64 release zip v0.14.1, unzip, copy lnav to ~/.local/bin

    cd /tmp && curl -fsSLO https://github.com/tstack/lnav/releases/download/v0.14.1/lnav-0.14.1-linux-musl-x86_64.zip && rm -rf lnavx && unzip -o -q lnav-0.14.1-linux-musl-x86_64.zip -d lnavx && mkdir -p ~/.local/bin && cp "$(find lnavx -type f -name lnav)" ~/.local/bin/lnav && chmod +x ~/.local/bin/lnav
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /tmp && curl -fsSLO https://github.com/tstack/lnav/releases/download/v0.14.1/lnav-0.14.1-linux-musl-x86_64.zip && rm -rf lnavx && unzip -o -q lnav-0.14.1-linux-musl-x86_64.zip -d lnavx && mkdir -p ~/.local/bin && cp "$(find lnavx -type f -name lnav)" ~/.local/bin/lnav && chmod +x ~/.local/bin/lnav
lnav -V
cd /home/sbx/work && cat > a.log <<'EOF'
Jan 10 10:00:00 hosta app[100]: starting service
Jan 10 10:00:02 hosta app[100]: error: connection refused
Jan 10 10:00:04 hosta app[100]: shutdown complete
EOF
cat > b.log <<'EOF'
Jan 10 10:00:01 hostb db[200]: listening on port 5432
Jan 10 10:00:03 hostb db[200]: error: disk full
Jan 10 10:00:05 hostb db[200]: checkpoint done
EOF
cd /home/sbx/work && lnav -n a.log b.log

Check that it works

lnav -V

The output should contain “lnav 0.14.1”.

First thing to try

cd "$HOME"/work && cat > a.log <<'EOF'
Jan 10 10:00:00 hosta app[100]: starting service
Jan 10 10:00:02 hosta app[100]: error: connection refused
Jan 10 10:00:04 hosta app[100]: shutdown complete
EOF
cat > b.log <<'EOF'
Jan 10 10:00:01 hostb db[200]: listening on port 5432
Jan 10 10:00:03 hostb db[200]: error: disk full
Jan 10 10:00:05 hostb db[200]: checkpoint done
EOF
cd "$HOME"/work && lnav -n a.log b.log

Run lnav <file> with one or more log files to open them in the viewer.

What it does

  • Merge log files into one time-ordered view
    How to use it
    1. Run lnav -n <file1> <file2> to print the lines of both files merged in time order.
    Tested
  • Jump to the previous or next error
    How to use it
    1. Run lnav -n -c ':goto 0' -c ':next-mark error' -c ':write-screen-to -' <file1> <file2> to jump from the top to the next error line and print the screen.
    Tested
  • Filter messages with a regex or SQLite
    How to use it
    1. Run lnav -n -c ':filter-in <pattern>' <file1> <file2> to show only lines that match the pattern.
    Tested
  • Analyze log messages with SQL queries
    How to use it
    1. Run lnav -n -c ';SELECT log_hostname, count(*) AS n FROM syslog_log WHERE log_level = '"'"'error'"'"' GROUP BY log_hostname' <file1> <file2> to count errors per host.
    2. Start the command with ; followed by your SQL query against the log tables.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 4 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • view systemd journal logs in a pager
  • merge multiple log files into one time-ordered view
  • tail log files and follow renames

An alternative to tail, grep and less.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version lnav 0.14.1

Differences the test machine hit

  • README: Build from source: ./configure; make; sudo make install (needs C++ compiler, many libs and cargo/rust)
    In the test: The prebuilt static binary from the release page (lnav-0.14.1-linux-musl-x86_64.zip) unzipped into ~/.local/bin works without root or toolchains
  • README: lnav /path/to/file1 ... opens the TUI
    In the test: Without a terminal, -n (headless) with -c commands was used to exercise features non-interactively

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.