The Unseen Librarian: On Grace Hopper and the First Bug Log

We talk a lot about logs. We parse them, index them, and set elaborate alerts based on their whispered secrets. We treat them as a given, a natural byproduct of our digital systems. But every practice, no matter how ingrained, has an origin story. And for the modern concept of logging an incident, we owe a quiet nod to a moment in 1947, inside the warm, humming belly of the Harvard Mark II computer.

The machine, a room-sized behemoth of relays and switches, was misbehaving. Calculations were failing, and the team was stumped. It was then that an operator, likely under the guidance of the formidable Commander Grace Hopper, investigated the physical machine itself. Deep within the intricate hardware, they found the culprit: a moth, its wings tragically splayed, lodged between the points of Relay 70. With a pair of tweezers, the insect was carefully extracted and, in a moment of pure instinct, taped into the Mark II’s logbook.

What strikes me about this event isn’t the now-famous pun of “debugging,” but the act of preservation itself. That technician didn’t just remove the fault; they documented it. They created a physical, undeniable record. They taped the moth next to the note, “First actual case of bug being found.” This was more than a joke; it was a log entry. It was evidence.

The First Post-Mortem

In that simple, almost whimsical act, they established a principle that is the bedrock of our work: incidents must be recorded with concrete evidence. They didn’t just say “the machine had a fault.” They provided the cause. They attached the artifact. They created a record that anyone else could examine, understand, and learn from. It was the world’s first hardware post-mortem, a story told not through vague recollection but through a tangible, preserved piece of the puzzle.

Today, we don’t tape moths into our ELK stacks. But the spirit of that first log entry is what we strive for every day. We are not just collecting lines of text; we are curating evidence. We are the unseen librarians of our systems, meticulously preserving the context of every stumble and crash so that the next person—or our future selves—can understand what truly happened. We are building a history, a narrative of the system’s life, one event at a time.

Grace Hopper’s team understood that to fix a problem, you must first truly see it, and then you must remember it. That taped-in moth is a monument to that ideal. It reminds us that our logs are not just data; they are the curated evidence of a system’s story, and our most reliable map for navigating the dark when things go wrong.

Notes & further reading

A few pages I came back to while writing this: