Apache Access Log — Common Format (log)
An Apache access log in the Common Log Format (CLF) — client, timestamp, request line, status, and byte count. Deterministic, with reserved documentation IPs. Paired with a Combined-format twin for testing log parsers.
192.0.2.99 - - [15/Jan/2026:08:00:36 +0000] "GET /images/logo.png HTTP/1.1" 301 21853
198.51.100.23 - - [15/Jan/2026:08:00:37 +0000] "DELETE /checkout HTTP/1.1" 301 51656
203.0.113.7 - - [15/Jan/2026:08:00:50 +0000] "GET /search?q=widgets HTTP/1.1" 301 8011
198.51.100.149 - - [15/Jan/2026:08:00:58 +0000] "PUT /static/app.css HTTP/1.1" 201 44193
203.0.113.130 - - [15/Jan/2026:08:01:21 +0000] "GET /login HTTP/1.1" 403 10666
198.51.100.23 - - [15/Jan/2026:08:01:44 +0000] "GET /favicon.ico HTTP/1.1" 304 0
198.51.100.149 - - [15/Jan/2026:08:02:19 +0000] "PUT / HTTP/1.1" 200 17295
203.0.113.201 - - [15/Jan/2026:08:02:51 +0000] "GET /favicon.ico HTTP/1.1" 404 7208
192.0.2.55 - - [15/Jan/2026:08:03:26 +0000] "HEAD /health HTTP/1.1" 200 7155
198.51.100.77 - - [15/Jan/2026:08:03:34 +0000] "GET /static/app.js HTTP/1.1" 404 23783
198.51.100.149 - - [15/Jan/2026:08:03:56 +0000] "POST /static/app.js HTTP/1.1" 301 18689
192.0.2.99 - - [15/Jan/2026:08:04:00 +0000] "GET /static/app.css HTTP/1.1" 200 37905
203.0.113.201 - - [15/Jan/2026:08:04:36 +0000] "GET /index.html HTTP/1.1" 404 51219
192.0.2.99 - - [15/Jan/2026:08:05:06 +0000] "HEAD /favicon.ico HTTP/1.1" 200 3593
192.0.2.10 - - [15/Jan/2026:08:05:19 +0000] "GET /api/orders HTTP/1.1" 201 26109
203.0.113.130 - - [15/Jan/2026:08:05:33 +0000] "POST /static/app.js HTTP/1.1" 500 44650
192.0.2.99 - - [15/Jan/2026:08:06:02 +0000] "HEAD /api/products/42 HTTP/1.1" 500 2420
203.0.113.7 - - [15/Jan/2026:08:06:05 +0000] "DELETE / HTTP/1.1" 200 25488
198.51.100.149 - - [15/Jan/2026:08:06:12 +0000] "GET /api/products/42 HTTP/1.1" 304 0
198.51.100.23 - - [15/Jan/2026:08:06:38 +0000] "GET /favicon.ico HTTP/1.1" 200 47888
198.51.100.77 - - [15/Jan/2026:08:07:00 +0000] "PUT /login HTTP/1.1" 201 31597
198.51.100.77 - - [15/Jan/2026:08:07:11 +0000] "HEAD /robots.txt HTTP/1.1" 304 0
203.0.113.130 - - [15/Jan/2026:08:07:14 +0000] "DELETE /images/logo.png HTTP/1.1" 304 0
203.0.113.7 - - [15/Jan/2026:08:07:30 +0000] "POST /robots.txt HTTP/1.1" 200 37170
192.0.2.99 - - [15/Jan/2026:08:07:42 +0000] "GET /search?q=widgets HTTP/1.1" 301 9085
192.0.2.99 - - [15/Jan/2026:08:08:19 +0000] "HEAD /favicon.ico HTTP/1.1" 500 48492
203.0.113.42 - - [15/Jan/2026:08:08:56 +0000] "POST /index.html HTTP/1.1" 200 35578
192.0.2.10 - - [15/Jan/2026:08:09:24 +0000] "GET /api/orders HTTP/1.1" 200 3175
203.0.113.42 - - [15/Jan/2026:08:09:37 +0000] "POST /static/app.css HTTP/1.1" 500 1082
198.51.100.149 - - [15/Jan/2026:08:10:15 +0000] "HEAD /images/logo.png HTTP/1.1" 500 15053
192.0.2.55 - - [15/Jan/2026:08:10:43 +0000] "GET /index.html HTTP/1.1" 304 0
203.0.113.130 - - [15/Jan/2026:08:11:01 +0000] "DELETE /index.html HTTP/1.1" 200 5464
198.51.100.23 - - [15/Jan/2026:08:11:04 +0000] "PUT /static/app.css HTTP/1.1" 200 13933
203.0.113.201 - - [15/Jan/2026:08:11:09 +0000] "PUT /static/app.css HTTP/1.1" 200 5288
192.0.2.55 - - [15/Jan/2026:08:11:47 +0000] "GET /login HTTP/1.1" 403 49983
203.0.113.42 - - [15/Jan/2026:08:11:56 +0000] "GET /images/logo.png HTTP/1.1" 200 42524
198.51.100.77 - - [15/Jan/2026:08:12:00 +0000] "GET /index.html HTTP/1.1" 500 8299
203.0.113.42 - - [15/Jan/2026:08:12:05 +0000] "DELETE /static/app.css HTTP/1.1" 500 45665
192.0.2.10 - - [15/Jan/2026:08:12:34 +0000] "GET /health HTTP/1.1" 304 0
192.0.2.10 - - [15/Jan/2026:08:12:52 +0000] "GET /static/app.css HTTP/1.1" 301 28301
203.0.113.42 - - [15/Jan/2026:08:13:21 +0000] "GET /search?q=widgets HTTP/1.1" 200 30008
192.0.2.55 - - [15/Jan/2026:08:13:43 +0000] "GET /login HTTP/1.1" 201 10741
203.0.113.201 - - [15/Jan/2026:08:13:58 +0000] "DELETE /health HTTP/1.1" 200 554
203.0.113.130 - - [15/Jan/2026:08:14:15 +0000] "GET /favicon.ico HTTP/1.1" 301 20319
198.51.100.77 - - [15/Jan/2026:08:14:32 +0000] "GET /static/app.css HTTP/1.1" 200 38603
Specifications
- Lines
- 45
- Format
- Common Log Format (CLF)
- Server
- Apache
- Seed
- 501
- Ips
- reserved TEST-NET (documentation)
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.
How to use this file for testing
“Apache Access Log — Common Format (log)” is a deterministic Novus Examples fixture for Log parsing, Data import, Observability. Access logs and JSON-lines application logs — for testing log parsers, tailers, and ingestion pipelines.
Documented properties for this file: seed 501 · Common Log Format (CLF). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks — delimiters, encodings, null handling, schema, and row counts — in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
grep -i error apache-common.log | head
awk '{print $1, $2, $NF}' apache-common.log | headRelated files
- logDocker Container Log — json-file driver (log)A Docker json-file container log — one JSON object per line with the log text, stream (stdout/stderr), and an RFC 3339 timestamp, exactly as Docker's default logging driver writes it. A fixture for container-log shippers and parsers.
- logKubernetes Component Log — klog (log)A Kubernetes-component log in the klog/glog format — a severity letter, timestamp, thread id, and source location prefix followed by the message. A fixture for testing klog parsers and severity extraction.
- logStructured Log — logfmt (log)A structured application log in logfmt — space-separated key=value pairs (ts, level, msg, method, path, status, duration, request_id) as used by many Go and Heroku-style services. A fixture for testing logfmt parsers.
- logSyslog Messages — RFC 3164 (log)A BSD-style syslog (RFC 3164) sample — timestamp, host, process and PID, then the message, across sshd, cron, kernel, nginx, and application entries. A fixture for testing syslog parsers and forwarders.
- log.NET Exception with an Inner Exception Chain (log)A .NET exception whose inner exception is introduced by the ---> marker and closed by End of inner exception stack trace, wrapped in pipe-delimited log lines. Error groupers that key on the outermost message alone merge two genuinely different faults here.
- jsonlAlert State History — Pending, Firing and Resolved Transitions (jsonl)Sixteen state transitions across four alerts, each moving inactive to pending to firing to resolved with the previous state recorded. The pending stage is where a for: duration is being served and no notification is sent, which is what makes alert-noise analysis possible.
Generated by generation/data_logs.py. Free for any use, no attribution required — license.