Generate synthetic Docker container logs

This sample, generated

The block below is 15 lines of Docker container logs, produced by the real generator at seed 42 — deterministic, so this exact output regenerates anywhere. The live tool re-runs the identical engine on whatever source, seed, line count and anomalies you pick.

Generated Docker container logs

Real on-the-wire Docker container logs — no real users, IPs, or secrets. Copy it into a fixture, feed it to a parser, or seed a SIEM demo.

With an anomaly injected: Port scan

The same source, regenerated with a Port scan injected at 30% intensity. 7 line sare tagged and highlighted below — One source IP hitting many sequential destination ports — reconnaissance sweeping for open services. It is a documented, detectable pattern your SIEM rules should fire on — build the test data, then prove your detection works.

FAQ

Are these real Docker logs?

No — the output is synthetic. It reproduces the dockerd logfmt line shape (time, level, msg, container, image, name) with realistic values, but every container, image and message is fabricated. Safe for fixtures, demos and parser tests.

Can I inject anomalies?

Yes. Raise any of the five sliders; for a key=value source a port scan is appended in faithful grammar, with the injected lines highlighted and badged so you can verify your detection fires.

Is the output deterministic?

Yes — fully seeded. The same seed and config always produce byte-identical Docker lines, so a committed seed regenerates the identical log anywhere.

Generate other log sources

• nginx access logs
• Apache access logs
• sshd / OpenSSH auth logs
• RFC 3164 (BSD) syslog
• RFC 5424 syslog
• FortiGate firewall logs
• Cisco ASA firewall logs
• Windows Security Event logs
• JSON application logs
• Kubernetes (klog) logs
• AWS VPC Flow logs

Open the LogAnvil generator to tune the seed, line count, EPS, format and anomaly sliders — or build a parser with LogForge for a log you already have.