Docker 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.
{"log": "Listening on :8080\n", "stream": "stdout", "time": "2026-01-15T12:00:03.533Z"}
{"log": "Listening on :8080\n", "stream": "stdout", "time": "2026-01-15T12:00:03.770Z"}
{"log": "cache hit key=session:abc\n", "stream": "stdout", "time": "2026-01-15T12:00:05.742Z"}
{"log": "WARN slow query 812ms\n", "stream": "stderr", "time": "2026-01-15T12:00:06.645Z"}
{"log": "connection pool size=10 in-use=3\n", "stream": "stdout", "time": "2026-01-15T12:00:09.663Z"}
{"log": "connection pool size=10 in-use=3\n", "stream": "stdout", "time": "2026-01-15T12:00:11.729Z"}
{"log": "ERROR upstream timeout\n", "stream": "stderr", "time": "2026-01-15T12:00:15.556Z"}
{"log": "connection pool size=10 in-use=3\n", "stream": "stdout", "time": "2026-01-15T12:00:17.112Z"}
{"log": "WARN slow query 812ms\n", "stream": "stderr", "time": "2026-01-15T12:00:19.877Z"}
{"log": "ERROR upstream timeout\n", "stream": "stderr", "time": "2026-01-15T12:00:21.671Z"}
{"log": "WARN slow query 812ms\n", "stream": "stderr", "time": "2026-01-15T12:00:24.600Z"}
{"log": "GET /api/products/999 404 5ms\n", "stream": "stdout", "time": "2026-01-15T12:00:25.309Z"}
{"log": "cache hit key=session:abc\n", "stream": "stdout", "time": "2026-01-15T12:00:28.741Z"}
{"log": "GET /api/products/999 404 5ms\n", "stream": "stdout", "time": "2026-01-15T12:00:31.548Z"}
{"log": "GET /health 200 3ms\n", "stream": "stdout", "time": "2026-01-15T12:00:31.762Z"}
{"log": "ERROR upstream timeout\n", "stream": "stderr", "time": "2026-01-15T12:00:34.445Z"}
{"log": "cache hit key=session:abc\n", "stream": "stdout", "time": "2026-01-15T12:00:37.395Z"}
{"log": "cache hit key=session:abc\n", "stream": "stdout", "time": "2026-01-15T12:00:40.383Z"}
{"log": "connection pool size=10 in-use=3\n", "stream": "stdout", "time": "2026-01-15T12:00:41.540Z"}
{"log": "cache miss key=products:42\n", "stream": "stdout", "time": "2026-01-15T12:00:41.850Z"}
{"log": "POST /api/orders 201 44ms\n", "stream": "stdout", "time": "2026-01-15T12:00:44.273Z"}
{"log": "cache miss key=products:42\n", "stream": "stdout", "time": "2026-01-15T12:00:45.088Z"}
{"log": "GET /api/products/999 404 5ms\n", "stream": "stdout", "time": "2026-01-15T12:00:45.456Z"}
{"log": "WARN slow query 812ms\n", "stream": "stderr", "time": "2026-01-15T12:00:47.829Z"}
{"log": "GET /api/products/999 404 5ms\n", "stream": "stdout", "time": "2026-01-15T12:00:50.575Z"}
{"log": "GET /health 200 3ms\n", "stream": "stdout", "time": "2026-01-15T12:00:53.734Z"}
Specifications
- Lines
- 26
- Driver
- json-file
- Schema
- log, stream, time
- Seed
- 504
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.
Related files
- logApache Access Log — Combined Format (log)An Apache access log in the Combined Log Format — the Common fields plus referer and user-agent. A realistic web-server log for testing access-log parsers, analytics, and grok patterns.

- logApache 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.

- 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.

- logJava Stack Trace (log)A realistic Java stack trace — a Spring-style NullPointerException with a nested 'Caused by' chain and '... N more' elision. A fixture for testing stack-trace parsers, error groupers, and log viewers.

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