I built TWSLA because I was tired of waiting for grep/awk on multi-gigabyte logs, and I didn't want to spin up a full ELK stack just for a quick analysis.
TWSLA is a single binary CLI tool that focuses on three things:
1. Speed: Blazing fast log parsing and counting.
2. Simplicity: One command to extract data or generate terminal-based graphs.
3. Portability: No dependencies, works on Windows, macOS, and Linux.
It handles Syslog, Apache/Nginx access logs, and custom formats easily. I've been refining this as part of my 25-year journey in network management tools.
Key features:
- High-speed filtering and counting
- Data extraction (IPs, Emails, etc.) via simple commands
- Built-in graphing capabilities (even in the terminal for some environments)
I'd love to hear how you currently handle "quick and dirty" log analysis and if TWSLA could fit into your workflow.
Hi HN,
I built TWSLA because I was tired of waiting for grep/awk on multi-gigabyte logs, and I didn't want to spin up a full ELK stack just for a quick analysis.
TWSLA is a single binary CLI tool that focuses on three things: 1. Speed: Blazing fast log parsing and counting. 2. Simplicity: One command to extract data or generate terminal-based graphs. 3. Portability: No dependencies, works on Windows, macOS, and Linux.
It handles Syslog, Apache/Nginx access logs, and custom formats easily. I've been refining this as part of my 25-year journey in network management tools.
Key features: - High-speed filtering and counting - Data extraction (IPs, Emails, etc.) via simple commands - Built-in graphing capabilities (even in the terminal for some environments)
I'd love to hear how you currently handle "quick and dirty" log analysis and if TWSLA could fit into your workflow.
GitHub: https://github.com/twsnmp/twsla
You don't need to repeat the post submission as a comment