reqlog

README

reqlog

Search and trace logs across services — fast.
Debug distributed systems without grep pipelines or context switching.

Why reqlog?

Debugging logs in microservices usually means:

• jumping between multiple files
• dealing with inconsistent formats
• writing fragile grep | awk | sort pipelines

reqlog fixes this in one command.

• Search logs across multiple services
• Match structured fields like request_id, trace_id
• Get a chronological flow of a request
• Visually scan logs with service-based colors

Quick Start

reqlog --dir ./logs --key request_id abc123

Example output:

2026-03-20T14:10:00Z [api-gateway]    | start request
2026-03-20T14:10:01Z [order-service]  | fetching order
2026-03-20T14:10:02Z [inventory]      | checking stock

Follow a request across services in seconds.

Features

• Key-based search (--key request_id)
• Fast scanning (millions of lines)
• Supports plain text + JSON logs
• Docker logs support
• Filter by service (--service, supports wildcards)
• Time filtering (--since)
• Colored output by service
• Live tailing (--follow)
• Case-insensitive search
• Works across multiple files & directories

Installation

Go Install

go install github.com/sagarmaheshwary/reqlog/cmd/reqlog@latest

macOS / Linux

curl -sSL https://raw.githubusercontent.com/sagarmaheshwary/reqlog/master/install.sh | bash

✔ Auto-detects OS/arch ✔ Installs latest version ✔ Installs to /usr/local/bin

Verify:

reqlog --version

Windows

Download from:

https://github.com/sagarmaheshwary/reqlog/releases

Then:

• unzip
• add to PATH

Verify:

reqlog --version

Usage

reqlog [flags] <search_value>

Basic Search

reqlog --dir ./logs abc123

Key-Based Search (Recommended)

reqlog --key request_id abc123
reqlog --key event_key order.created

JSON Logs

reqlog --dir ./logs --json --key trace_id trace-123

Docker Logs

reqlog --source docker --service api-gateway abc123

Wildcard support:

reqlog --service order-service* abc123

Time Filtering

reqlog --since 10m --key request_id abc123

Follow Logs (Live)

reqlog --follow --key request_id abc123

Why not just use grep?

Problem	grep	reqlog
Multi-file search	⚠️ manual	✅ built-in
Request tracing	❌	✅
JSON logs	❌	✅
Chronological flow	❌	✅
Service context	❌	✅

reqlog = grep for distributed systems

Performance

• ~9.6M lines scanned in ~2 seconds
• ~9 MB memory usage
• Works efficiently on real-world datasets

Optimized for sequential reads + minimal memory usage

Supported Log Formats

Text Logs

• ISO-8601 timestamp at start
• key=value fields

2026-03-20T14:00:00Z request_id=abc123 start request

JSON Logs

• One JSON per line
• Timestamp fields: time, timestamp, ts

{ "time": "2026-03-20T14:10:00Z", "request_id": "abc", "message": "start" }

Roadmap

• Docker support
• Kubernetes logs
• Parallel scanning
• More log formats

Contributing

Contributions and feedback are welcome!

License

MIT