Does this log analyzer upload files?
No. Log files are parsed locally in the browser, which is useful when your production logs contain real IPs, query strings, and internal routes.
Local Analysis
Log Analysis
That Stays Local
Open your logs in the browser and see traffic, errors, slow requests, bots, and top paths in a few seconds.
This tool works with Nginx, Apache, Caddy, and HAProxy logs. Your files stay on your machine. Nothing is sent to a server. You can filter by time, search raw lines, check status codes, and review charts without leaving the page.
Nginx Logs
Open access logs and inspect traffic, errors, bandwidth, and top paths.
Apache Logs
Review request volume, client IPs, status codes, and common problem URLs.
Caddy Logs
Read JSON logs and check request time, traffic volume, and source breakdowns.
HAProxy Logs
Check backend traffic, response time, status codes, and heavy paths.
Instant Processing
Stream-based parsing handles 100MB+ logs in seconds using multi-threaded Web Workers.
Threat Detection
Built-in detection rules identify malicious IP behavior, directory scanning, and bot anomalies.
Clear Charts
See traffic by time, status code, source, user agent, and path with simple charts and tables.
What You Can Do
Upload a log file and the page will build charts for traffic, unique visitors, request volume, error rate, and bandwidth. You can zoom into the timeline, filter by method or status code, and search raw lines.
This is useful for debugging outages, checking crawler traffic, finding noisy clients, reviewing bad URLs, and spotting unusual spikes after deploys or config changes.
Common Uses
- Check what happened during a traffic spike or outage.
- Find the top error URLs, status codes, and source IPs.
- Review crawler and bot traffic without sending logs anywhere.
- Compare busy paths, slow paths, and heavy bandwidth endpoints.
When To Use It
Use this tool when you need to understand traffic spikes, error sources, suspicious scans, crawler requests, or heavy URLs directly from raw logs in the browser.
It is useful for post-deploy traffic review, 4xx and 5xx troubleshooting, hot-path analysis, bot detection, and auditing sensitive production logs without uploading files.
What You Can Inspect
Status distributionTraffic timelineTop pathsSuspicious scansCrawler activitySlow requestsSource IPsBandwidth usage
FAQ
Common questions around log analysis, privacy, and incident review.
What problems is it useful for?
You can inspect crawler requests, 404 pages, 5xx failures, redirect behavior, and heavily requested URLs to find traffic and site issues quickly.
Which log formats are supported?
It currently supports Nginx, Apache, Caddy, and HAProxy logs with a shared workflow for traffic, error, and threat analysis.