The Unwritten Ledger: On the Ethics of What We Choose Not to Log
We spend so much of our time obsessing over what we log. We debate the merits of structured versus unstructured, argue over retention periods, and tune our filters to capture every last whisper of system state. This is our craft, and we are right to be diligent. But in our pursuit of a perfect record, we rarely pause to consider the other side of the coin: the profound responsibility of what we consciously decide to omit.
Every logging configuration is, in its own quiet way, a moral document. It is a declaration of what we, as stewards of these systems, deem worthy of remembrance and what we sentence to oblivion. We speak often of the 'lie of the silent log,' where a failure goes unseen because we failed to capture its signal. But there is a parallel, more subtle truth: the lie of the absent log, where a thing is unseen because we deemed it unworthy of being seen.
The Deliberate Silence
This is not about storage costs or performance overhead. This is about intentionality. Consider a user authentication service. We log the failed attempts, of course—the time, the IP, the username. This is necessary for security. But do we log the successful ones? The argument against is sound: it’s noise, it’s volume, it’s a privacy risk. But in choosing not to log it, we are making a conscious decision to erase the proof of a person’s presence at a specific moment. We are creating a system that cannot bear witness to their passage.
This is not inherently good or bad. It is simply a choice with weight. It is an ethical configuration. We build systems that see everything, but we must also build the blinds. We must ask ourselves: if this data point could one day be used to harm, to misrepresent, or to persecute, is our duty to capture it or to protect our users from its existence? There is no easy answer, only a question that must be asked at the whiteboard, long before a line of configuration is written.
This extends beyond user data. What about the internal health checks between services? Do we log every single 'pong'? To do so is to create a sea of monotony in which a true failure might drown. To not do so is to accept that a slow, degrading death by a thousand timeouts will leave no individual trace, only a collective, inferred symptom. We are choosing the narrative of our system’s life. Will it be a detailed diary or a series of dramatic cliff notes?
The logs we keep tell us what went wrong. But the logs we deliberately exclude tell a story, too—a story about our priorities, our fears, and our principles. They speak of the things we are willing to forget. In our quest for reliability, we must remember that the most powerful entry in any ledger is sometimes the one that was never written. Our silence is as much a part of the design as our noise.
Notes & further reading
A few pages I came back to while writing this: