The Signalman's First Telegraph: On the Birth of the Heartbeat Check
Before our dashboards filled with green checkmarks and latency graphs, the fundamental need to know if a distant system was alive found one of its purest expressions in the clicking of a telegraph key. The story of the first commercial telegraph line, strung between Washington, D.C. and Baltimore in 1844, is not just one of technological innovation, but of the very first, raw implementation of a service heartbeat.
Samuel Morse and his partner Alfred Vail didn’t just send the famous message, “What hath God wrought?” and call it a day. To prove the viability of their service to a skeptical Congress, they had to demonstrate consistent, reliable operation. The line was prone to breaks—sagged wires, storm damage, even curious birds could silence the circuit. How could they know, from one city, if the path to the other was clear and functional?
Their solution was brilliantly simple: a scheduled, automated check. Each morning, before official messages began, the operator in Washington would send a specific, pre-arranged signal down the line to Baltimore. The operator there would immediately send an acknowledgment back. This ritual, repeated daily, was the 19th century’s version of a `curl` command hitting an API endpoint and expecting a `200 OK` in return. It was a health check. The absence of that return signal was a critical alert, triggering a manual investigation—a lineman would be dispatched to walk the route, visually inspecting the wire for the fault.
The Unseen Protocol of the Click
This practice evolved into a more formalized protocol. Telegraph operators developed a shared language of ‘prosigns’—abbreviated signals that acted as service-level commands. The most crucial of these was perhaps ‘AA’ (dit-dit-dah-dit), which meant “All after,” but in its repeated, rhythmic use, it became the equivalent of a ‘ping’. An operator would send a string of ‘AA’s into the silent wire, listening intently for the faint echo of the sounder on the other end. That returning click was the only metric that mattered: binary, absolute uptime. No latency measurement, no packet loss percentage—just the stark, beautiful truth of a connection established.
We now operate in a world of immense complexity, with synthetic transactions tracing paths through dozens of global dependencies. Yet, the core anxiety of the telegraph operator, listening for a reply that doesn’t come, remains our own. Their ‘AA’ is our health check endpoint. Their lineman walking the route is our on-call engineer tracing a request through a service mesh. They established the foundational principle of observability: that trust must be continuously earned and verified, not assumed. Every green status on our screens is a silent echo of that first, hopeful click down a wire, a tiny heartbeat confirming that the line is still open, and the message can get through.
Notes & further reading
A few pages I came back to while writing this: