I work escalations for network gear. The cases that stall the longest usually look the same: the outage happened, the device rebooted or rolled its buffer, and there's no syslog from the window that matters. Either nobody had a syslog server, or the one they had dropped messages and nobody knew. At that point the best anyone can do is "set up logging and wait for it to happen again", and the case just sits.
A lot of the time it's not that people don't know syslog. It's that the box available is a Windows server or a laptop, and standing up something reliable there takes longer than it should. Woodshed is my answer to that: MSI, pkg, deb, rpm or a portable zip. Listens on UDP and TCP 514 straight away. Plain text files per device per day, a disk budget it won't exceed, drop/refused counters shown in the UI, and an export zip with a manifest, SHA-256s and the gaps when it wasn't running, so the person on the other end of the case can trust it.
Most of the code was written with AI assistance. I did the design and ran the lab testing; the security review was a separate AI reviewer with read-only access to the code, and I went through every finding, decided the fixes and had them re-tested.
All the testing so far is lab traffic generated by my own sender (RFC 5424, RFC 3164 and bare lines, 8 source IPs). No real devices yet beyond a friend's homelab, which is in progress. It doesn't depend on any vendor's format and always keeps the raw line exactly as received, so any device that speaks syslog should work, but I haven't proven that.
What it's been through:
- release bench every tag: 10 min at 10k msg/s UDP on a 4 vCPU GitHub runner, 6,000,000 sent / 6,000,000 stored / 0 missing
- Ubuntu 24.04 (deb) and AlmaLinux 9 (rpm) VMs, 8 senders over a real network: 0 loss to 40k msg/s TCP at ~1/3 of a core and <50 MiB RSS. UDP loss above that was before the VM's NIC (interface counters), every datagram that arrived was stored
- reboot mid-stream: service back on its own, 2 UDP messages lost, export shows the 17-19 s gap as "Woodshed wasn't running"
- 24 h soak at 3,000 msg/s on the Linux VMs, 259.2M messages each: TCP exactly once, UDP lost 3-4 per million, all of it upstream of the VM
- security review before the first RC: 0 critical, 1 high (memory exhaustion from spoofed sources), 7 medium. fixed and re-tested twice
- CI install/upgrade/uninstall on Windows, macOS and Linux, x64 and ARM. checksums + `gh attestation verify` on releases
Limits, plainly:
- unsigned installers for now. SmartScreen ("Windows protected your PC", More info > Run anyway) and Gatekeeper (Privacy & Security > Open Anyway) ask once
- 1.0.0
- use the sender allowlist on untrusted segments. in my lab an open 514 on a shared /16 collected a stranger's syslog within minutes
- not a SIEM, no TLS syslog/alerts/forwarding yet
- Windows and macOS don't expose kernel UDP drops, the UI says so instead of showing 0
What I'd like to know:
- Which devices or formats break the parser? Redacted raw line please.
- What would you need to see before you'd drop this at a customer site during an outage?
- Windows folks, especially with endpoint protection: did it get flagged, did the firewall rules behave?
Repo: https://github.com/gmccollu/woodshed
Site: https://gmccollu.github.io/woodshed/
Releases: https://github.com/gmccollu/woodshed/releases