Every team running high-volume log pipelines eventually hits the same wall: PII leaks into logs faster than anyone can write regex for it. The usual fix — a naive redaction filter bolted onto the log shipper — solves the compliance problem and creates a new one. Memory climbs. CPU spikes. Sender nodes start falling over under load, and now you’re debugging your debugging tool.

We lived that incident. A Lua-based PII redaction filter on production log senders pushed memory from 130MB to 900MB and CPU from 39% to 97% under normal traffic. Removing the filter fixed the resource problem and broke the compliance one right back open.

That gap between compliant logs and debuggable, performant infrastructure is what Osmium exists to close.