Log Inspector

Find errors, slow requests, and where traces spend their time in your logs, and open the lines behind every count.

Your data stays in your browser

Logs to inspect

.log, .txt, .json, or .jsonl, up to 10.0 MB. Or drop a file on the text area. Files are read in your browser.

Paste logs or open a file

Log inspection

No result

Paste logs in Logs to inspect, or open a log file.

Example

Automatic reading

Input

ts=2026-09-24T10:00:01Z level=error service=payment msg="Payment 81 timed out"
ts=2026-09-24T10:00:02Z level=info service=order msg="Order 12 created"
ts=2026-09-24T10:00:05Z level=error service=payment msg="Payment 93 timed out"

Output

ERROR 2 · INFO 1
Payment {id} timed out · 2 events
payment · 2 errors

How it works

Reads JSON, key-value pairs and logfmt, trace-context lines, Spring Boot, Logback, Log4j, and Python logs, syslog and journald, and Nginx, Apache, and IIS logs, even mixed or inside Docker and Kubernetes output. For any other layout, write a pattern or paste your Logback one. Stack traces join their event, and unread lines are counted, never dropped.
Counts levels, groups exceptions and repeated messages into templates such as User {id} not found, and marks error bursts over time.
With a correlation or request ID, it lists requests by observed duration, with a timeline per service and possible retries. Endpoints get p50 to p99.
With trace and span IDs, it draws each trace as a tree and a waterfall, shows the critical path and the largest latency contributor, and maps the calls between services.
Every count opens the log lines behind it. Filter by time, level, service, or text, then copy or download the matching lines. Paste logs or open a .log file: nothing is uploaded.

1Logs to inspect