Observability 2.0, Dev Tools, and Debugging
A better approach to system understanding and solving unknown unknowns.
đ Hi, this is Thomas. Welcome to a new edition of Beyond Runtime, where I dive into the messy, fascinating world of distributed systems, debugging, AI, and system design. All through the lens of a CTO with 20+ years in the backend trenches.
QUOTE OF THE WEEK:
âObservability is the process through which one develops the ability to ask meaningful questions, get useful answers, and act effectively on what you learnâ - Hazel Weakly
I was recently interviewed for a three-part series on MonkCast, RedMonkâs podcast, where I discussed Observability 2.0, dev tools and debugging with KellyAnn Fitzpatrick.
Hereâs my summary â and a few more thoughts â of that conversation.
Only a few short years ago, we were debating the definition of observability. Now the term has been taken up by APM vendors (and marketing teams of all kinds) to the point that it seems rather ubiquitous.
Partly in reaction to this, we have heard folks--including thought leaders in the space, such as Charity Majors at Honeycomb--take up the term "Observability 2.0": a developer-centric approach designed to empower teams throughout the software development lifecycle (SDLC).
From Observability 1.0 to 2.0
To understand Observability 2.0, letâs look at where weâve been.
Observability 1.0 refers to the traditional approach where vast amounts of telemetry data (metrics, logs, and traces) is collected and then displayed with dashboards - i.e. using APM tools. These tools are great for detecting known unknowns and spotting trends in production. But they often leave developers sifting through mountains of data, piecing together insights like searching for a needle in a haystack.
Observability 2.0 redefines this paradigm. It emphasizes real-time, actionable insights across the entire SDLC. Instead of simply monitoring for problems, it helps developers understand system behaviors, revealing the unknown unknowns.
The evolution of how we think and implement observability reflects the growing complexity of modern software systems and the need for more sophisticated tools to manage and understand them.
Why Observability 2.0 Matters for Developers
For developers, Observability 2.0 offers more than just improved system monitoring. It transforms how they work by reducing friction, improving productivity, and fostering a deeper understanding of their systems. Hereâs how:
1. Enhanced Developer Experience
Developer experience (DX) goes beyond productivity; itâs about making developersâ lives easier, more efficient, and more fulfilling. Observability 2.0 addresses key DX challenges, such as:
High cognitive load: Complex systems with scattered, outdated documentation can overwhelm developers. Observability 2.0 reduces this load by providing a unified, real-time view of the system.
Disruptions to flow state: Debugging with traditional tools often pulls developers out of deep focus. Observability 2.0 minimizes these disruptions by streamlining problem-solving.
Feedback loops: Instant insights into how changes affect the system help developers iterate faster, avoiding costly mistakes.
2. Simplified Debugging
Traditional debugging involves reproducing issues, sifting through logs, and piecing together context across tools. Observability 2.0 changes the game. For example, Multiplayerâs Platform Debugger, powered by OTel, captures deep session replays that include both frontend and backend data. Developers can pinpoint issues quickly, reducing manual effort and saving hours (or days) of frustration.
3. Cost Savings and Team Productivity
There is a very real financial toll linked to manual and ineffective work. According to a recent Atlassian survey, developers are losing 8+ hours a week due to inefficiencies, which is about $13k per developer per year. In a team of 400 engineers, these costs can balloon to $5M annually!
The Future of Observability
Modern software systems are increasingly complex, with interdependent internal and external services. As the ecosystem grows, Observability 2.0 will mean more visibility into your distributed system and less manual work.
Looking ahead to 2025 and beyond, I believe that observability 2.0 will continue to empower developer teams by automating complex troubleshooting processes, enabling rapid onboarding, and reducing knowledge silosâultimately saving organizations time, money, and engineering effort.
This is the full conversation with KellyAnn Fitzpatrick:
đ This newsletter is sponsored by Multiplayer.app.
Full stack session recording. End-to-end visibility in a single click.
đ Interesting Articles & Resources
The best way to test Web APIs - Daniel Moka
This article explores the best practices for testing web APIs, emphasizing two approaches: Solitary vs Sociable API tests.
How we built the Tinder API Gateway - Tinder Engineering Team
Tinder has 500 microservices which talk to each other for different data needs using a service mesh under the hood. This article delves into how Tinder's API Gateway was designed to streamline communication between clients and backend services.
Lidlâs Cloud Gambit: Europeâs Shift to Sovereign Computing - Dotan Horovits
Lidl is a European grocery discount retailer which has recently boldly entered into the cloud computing market with its Eurocloud initiative, challenging giants like AWS and Microsoft.
Technical Debt Examples & Tutorial - Thomas Johnson
This article goes beyond the usual high-level discussions and provides real-world examples of technical debtâranging from code-level issues to architectural and documentation debt.