Nerdlog

Nerdlog is a fast, remote-first, multi-host TUI log viewer with timeline histogram and no central server. Loosely inspired by Graylog/Kibana, but without the bloat. Pretty much no setup needed, either.

Nerdlog screenshot 1

Cost / License

  • Free
  • Open Source

Platforms

  • Go (Programming Language)
  • Windows
  • Mac
  • Linux
  • BSD
-
No reviews
0likes
0comments
0news articles

Features

Suggest and vote on features

Properties

  1.  Privacy focused
  2.  Lightweight

Features

  1.  Command line interface
  2.  No Tracking
  3.  No registration required
  4.  Ad-free
  5.  Multi-host
  6.  Visual timeline
  7.  Timeline
  8.  Tui
  9.  Timeline-based

 Tags

  • log-viewer
  • histogram

Nerdlog News & Activities

Highlights All activities

Recent activities

Show all activities

Nerdlog information

  • Developed by

    Dmitry Frank
  • Licensing

    Open Source (BSD-2-Clause) and Free product.
  • Written in

  • Alternatives

    43 alternatives listed
  • Supported Languages

    • English

AlternativeTo Categories

Network & AdminOS & Utilities

GitHub repository

  •  1,366 Stars
  •  35 Forks
  •  15 Open Issues
  •   Updated  
View on GitHub

Popular alternatives

View all
Nerdlog was added to AlternativeTo by Paul on and this page was last updated .
No comments or reviews, maybe you want to be first?
Post comment/review

What is Nerdlog?

Nerdlog is a fast, remote-first, multi-host TUI log viewer with timeline histogram and no central server. Loosely inspired by Graylog/Kibana, but without the bloat. Pretty much no setup needed, either.

It's laser-focused on being efficient while querying logs from multiple remote machines simultaneously, filtering them by time range and patterns, while also drawing a timeline histogram for quick visual insight.

Primary use case: reading system logs (/var/log/messages or /var/log/syslog) from one or more remote hosts. Very efficient even on large log files (like 1GB or more).

It does support some other log formats and can use any log files, but that was the primary use case which was driving the implementation: we were having our web service backend running as systemd services on a bunch of Linux instances, printing a lot of logs, and wanted to be able to read these logs efficiently and having the timeline histogram, much like tools like Graylog have.

Official Links