I'm Joseph Tracy, an infrastructure engineer in Seattle with over two decades across enterprise systems: PowerScale, Isilon, OneFS, and the Linux internals that keep large-scale storage environments running under pressure. I have spent the last two years building the automation layer on top of that operational foundation, turning deep hands-on knowledge into repeatable, documented, version-controlled systems.
The tooling here is small and single-purpose, aimed at the operational problems that keep recurring: the check that should have run before the job started, the snapshot that should have been taken before the config changed, the timing history that turns "it feels slow" into a measurement. Each one ships tested, documented, and with its source.
Everything here is built and tested on my own time. This site is where that work gets done in public.
Featured
The shared reliability plumbing extracted from my monitoring scripts: dependency preflight, locking with guaranteed cleanup, temporary directories that cannot leak, structured logging, and retry with backoff. Not a framework. A library with exactly the functions its two consumers earned.
The mechanical first hour of incident log review, automated: takes log files from multiple systems, normalizes their timestamps to UTC, corrects known clock drift per source, brackets a window around an anchor time, and emits one merged, time-sorted stream so a human can start reading instead of collating.
A manifest-driven environment checker that runs before real work does: required commands exist, paths are readable or writable, variables are set, disk has room, the clock is synced. Every failure reported at once, in plain language, so a broken environment is a readable report instead of a mid-run mystery.
A data-path canary for NFS exports and SMB shares. It mounts, writes, reads back, verifies, deletes, and unmounts, timing every phase in milliseconds, and appends the results to a CSV history so "the share feels slow" becomes a question with a baseline instead of a vibe.
Weighted systems need modernization too, just translated for infrastructure that will never be disposable. Five practices that survive the crossing, what each one turns into on the other side, and the failure mode each one carries.
Observability Meets the Filesystem
The 2026 observability doctrine wants everything streamed continuously. At the filesystem the physics push back, and scheduled batch collection turns out to be the correct engineering response rather than the un-modernized one.
Why Change Management Is Deliberately Slow
Deployment frequency is the celebrated metric of the age, so an hour spent on one paragraph of a change plan looks like pathology. Sometimes it is. Sometimes it is the most rational activity in the building, and what separates the two cases is weight rather than maturity.
