Log analysis / hour & weekday traffic modeling

Find out exactly when your server sweats.

Point this at NASA-HTTP or Apache-format access logs and it reads the request timestamps to surface peak hours, the busiest weekday, and a full hour-by-day heatmap — no server, no database.

Peak hour

—

busiest 60-minute window

Peak day

—

highest total requests

Total requests

—

parsed from log

Days logged

—

Traffic by hour of day

00:00 - 23:00, all days combined

Hour × weekday heatmap

brighter = more requests

Quiet Peak

Traffic by day of week

Monday → Sunday

Top requested paths

from parsed request lines

Response status codes

—

Response status codes decoded

—

HTTP Status Code 200 (OK) means that the request was successful.
HTTP Status Code 302 (Found) means that the requested resource has been temporarily moved to a different URL.
HTTP Status Code 304 (Not Modified) means that the requested resource has not changed since the last time the browser downloaded it.
HTTP Status Code 404 (Not Found) means that the server could not find the requested resource (webpage, image, file, etc.).
HTTP Status Code 500 (Internal Server Error) means that the server encountered an unexpected problem while processing the request.

How this works

01 · Parse

A regular expression reads each line of a Common/Combined Log Format access log — the format used by both the 1995 NASA-HTTP logs and the Kaggle Apache logs dataset — and pulls out the request timestamp.

02 · Aggregate

Every request is bucketed by hour-of-day (0–23) and weekday (Mon–Sun), building a 7×24 matrix alongside simple hourly and weekday totals.

03 · Render

The aggregated JSON drives two bar charts and a heatmap — client-side only. Drop your own log above and it's parsed entirely in your browser; nothing is uploaded anywhere.