The Problem
Reading log files in a terminal is a raw experience. Dates, IP addresses, UUIDs, and error keywords all render in the same monochrome text, making it hard to spot anomalies or trace a request across multiple lines. Engineers typically resort to grep pipelines or IDE plugins, which either strip context or require per-project configuration.
What This Does
tailspin is a Rust-based log highlighter that reads a log stream line-by-line and applies regex-based highlighting to recognized patterns. It lives in src/core/highlighters/ with dedicated modules for dates, IPs, UUIDs, URLs, key-value pairs, Unix paths, and processes. The src/io/ module handles input from files, stdin, or an executed command (--exec), and output to stdout or a less pager.
The tool requires zero configuration. It makes no assumptions about log format or field position, so highlighting works consistently across different log sources. All highlight groups are customizable via a theme.toml file, and the project is also published as a reusable crate.
How To Use It
Setup: Install via cargo install tailspin, or use a package manager (Homebrew, pacman, Nix, scoop). Build from source with cargo install --path . — the binary is tspin.
Configuration: Optional. Create ~/.config/tailspin/theme.toml to override styles for any highlight group. The config.toml in the repo root shows the default settings.
Running it: View a file in less tspin application.log
Pipe stdin to stdout
kubectl logs [podname] --follow | tspin
Run a command and view output in less
tspin --exec='kubectl logs -f podname'
Real-World Use
In a Kubernetes debugging session, you can pipe pod logs through tspin to get color-coded timestamps and error keywords while preserving the full log stream. The --exec flag is useful for wrapping a live kubectl logs -f command directly. For local development, running tspin on an application log file gives the same visual parsing without leaving the terminal.
Code Health & Issues
The codebase is well-structured with clear separation of concerns: src/core/ for highlighting logic, src/io/ for input/output, and src/theme/ for configuration. Tests exist in tests/integration_tests.rs and src/core/tests/, CI runs in .github/workflows/BuildAndTest.yml, and a lockfile is committed. No obvious structural red flags. Low - The regex-based highlighting approach is inherently fragile for complex or malformed log lines; performance on very large files may degrade. The src/core/highlighters/ modules each handle a single pattern, which is clean but means many regex passes per line. Low - The --exec command wrapping relies on the external less pager being present and up-to-date, as noted in the README. This is a documented dependency rather than a hidden risk. Med - No explicit input size limits or backpressure handling in src/io/reader/; a very fast stdin stream could cause memory pressure, though the line-buffered design mitigates this.
The Bottom Line
tailspin is a focused, well-implemented tool that does one thing well: making log files readable in a terminal. It is not a log analysis platform — no filtering, searching, or aggregation — but for developers who live in a shell, it removes a daily annoyance with minimal setup. The codebase is clean, tested, and maintained. If you spend time reading logs in a terminal, this is worth installing.