Skip to content
Novus Examples
log398 B

Nginx Access Log

An nginx combined-format access log with several requests, including a 403 and a 404 — for testing log parsers.

Preview — first 5 lineslog
127.0.0.1 - - [01/Jan/2026:09:00:01 +0000] "GET /index.html HTTP/1.1" 200 1024 "-" "Mozilla/5.0"
127.0.0.1 - - [01/Jan/2026:09:00:02 +0000] "GET /style.css HTTP/1.1" 200 512 "http://localhost/" "Mozilla/5.0"
203.0.113.7 - - [01/Jan/2026:09:00:03 +0000] "POST /api/submit HTTP/1.1" 403 89 "-" "curl/8.0"
203.0.113.7 - - [01/Jan/2026:09:00:04 +0000] "GET /missing HTTP/1.1" 404 153 "-" "Mozilla/5.0"

Specifications

What is a .log file?

LOG files are plain-text records of events emitted by software, typically one entry per line with a timestamp, severity, and message. There is no single standard, so formats range from unstructured text to structured JSON lines. They are central to debugging, monitoring, and auditing.

How to use this file

Use an example LOG file to test log parsers, timestamp and severity extraction, line-oriented streaming, and ingestion into monitoring or analysis pipelines.

Generated by generation/data_formats.py. Free for any use, no attribution required — license.