The Cartographer's Fixed Landmark vs. The Explorer's Shifting Compass: On the Dueling Maps of Uptime and Observability
We build our services on a map we have drawn ourselves. We plot the coordinates of critical functions, mark the ports, and define the routes a request should travel. To ensure this map reflects a livable world, we plant flags. These are our uptime checks—precise, synthetic transactions that travel a known path to a known destination, confirming the landmarks are exactly where we left them. The server is up. The database accepts a connection. The API returns a 200 OK for a specific query. It is the cartographer’s satisfaction, verifying that the coastline hasn’t crumbled into the sea.
This is a vital, reassuring practice. A fixed landmark tells you, with binary certainty, that a specific point is reachable. But a map is not the territory. It is a frozen representation of a living, shifting ecosystem. What of the marshes that have grown more treacherous since the last survey? What of the new, unofficial paths worn by travelers that now handle more traffic than the royal road? The fixed landmark is blind to this. It confirms the existence of the bridge but cannot feel its new, unsettling sway under a heavier load.
This is where the explorer’s compass enters the fray. Observability is not about checking pre-drawn points; it’s about venturing into the wilderness with instruments that measure the environment itself. It is the compass of metrics, the sextant of traces, and the journal of logs that record the journey, not just the destination. It asks not “is the landmark there?” but “what is the nature of the terrain between here and there?”
The two approaches are not enemies; they are partners in a necessary, creative tension. The uptime check is our hypothesis: “The login service is healthy.” Observability is the experiment that proves or disproves it, providing the context for the result. That 200 OK from the login endpoint is a fixed landmark. But the explorer’s compass—the detailed trace—might reveal that while the landmark stands, the journey to it now wades through a bog of newly introduced database latency, a detail the simple map could never show.
Relying solely on the cartographer’s landmark breeds a fragile confidence. The map says all is well, until suddenly the entire continent is missing. Conversely, possessing only the explorer’s compass can lead to paralysis in a sea of data without a clear heading. The true art lies in their synthesis. Use the fixed landmarks to declare a state of emergency, and use the shifting compass to navigate your way to the root of the trouble. Let your uptime checks sound the alarm that the world has diverged from your map, and let your observability tools draw you a new one, in real-time, that reflects the truth of the living system you serve.
Notes & further reading
A few pages I came back to while writing this: