Kubernetes 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.
W0115 09:30:02.436000 9 handler.go:287] request method=GET path=/api/products/999 status=404
I0115 09:30:04.667000 10 server.go:399] Starting API server, version=1.4.2
I0115 09:30:05.283000 13 reconcile.go:213] reconcile loop completed objects=42 duration=88ms
I0115 09:30:07.302000 7 server.go:144] Starting API server, version=1.4.2
W0115 09:30:08.167000 28 handler.go:276] request method=GET path=/api/products/999 status=404
W0115 09:30:08.711000 9 handler.go:390] request method=GET path=/api/products/999 status=404
I0115 09:30:11.114000 19 handler.go:108] request method=POST path=/api/orders status=201
I0115 09:30:12.150000 27 handler.go:341] request method=GET path=/healthz status=200
I0115 09:30:14.006000 2 handler.go:268] request method=POST path=/api/orders status=201
I0115 09:30:15.900000 27 cache.go:329] cache warmed keys=128
W0115 09:30:18.131000 12 pool.go:178] connection pool nearing capacity in-use=9 max=10
I0115 09:30:19.672000 7 shutdown.go:206] received SIGTERM, draining connections
W0115 09:30:21.152000 14 pool.go:330] connection pool nearing capacity in-use=9 max=10
I0115 09:30:23.625000 14 handler.go:381] request method=POST path=/api/orders status=201
I0115 09:30:24.746000 20 shutdown.go:53] received SIGTERM, draining connections
I0115 09:30:25.083000 24 reconcile.go:364] reconcile loop completed objects=42 duration=88ms
W0115 09:30:26.457000 6 pool.go:303] connection pool nearing capacity in-use=9 max=10
E0115 09:30:28.867000 5 upstream.go:298] upstream call failed: context deadline exceeded
I0115 09:30:29.899000 7 cache.go:226] cache warmed keys=128
I0115 09:30:32.663000 19 reconcile.go:183] reconcile loop completed objects=42 duration=88ms
I0115 09:30:34.446000 16 server.go:53] Starting API server, version=1.4.2
E0115 09:30:37.020000 2 upstream.go:399] upstream call failed: context deadline exceeded
I0115 09:30:38.077000 12 config.go:351] loaded configuration from /etc/app/config.yaml
I0115 09:30:38.594000 29 handler.go:311] request method=GET path=/healthz status=200
W0115 09:30:40.116000 4 handler.go:210] request method=GET path=/api/products/999 status=404
I0115 09:30:42.352000 26 cache.go:347] cache warmed keys=128
W0115 09:30:43.351000 19 handler.go:299] request method=GET path=/api/products/999 status=404
I0115 09:30:46.177000 2 cache.go:315] cache warmed keys=128
Specifications
- Lines
- 28
- Format
- klog (glog)
- Schema
- Lmmdd hh:mm:ss.uuuuuu threadid file:line] msg
- Seed
- 505
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
“Kubernetes Component Log — klog (log)” is a deterministic Novus Examples fixture for Log parsing, Observability. Access logs and JSON-lines application logs — for testing log parsers, tailers, and ingestion pipelines.
Documented properties for this file: seed 505 · schema: Lmmdd hh:mm:ss.uuuuuu threadid file:line] msg · klog (glog). 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 k8s-klog.log | head
awk '{print $1, $2, $NF}' k8s-klog.log | headRelated 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.
- 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.
- 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.
Generated by generation/data_logs.py. Free for any use, no attribution required — license.