New York

October 15–17, 2025

Berlin

November 3–4, 2025

London

June 2–3, 2026

What observability 2.0 means for developer experience 

The evolution of observability has brought in an exciting new reality when it comes to developer experience.
November 27, 2024

Estimated reading time: 5 minutes

As observability 1.0 evolves into observability 2.0, questions arise about how this new approach can save money, time, and improve developer experience. 

The journey from observability 1.0 to observability 2.0 reveals the struggle to define observability and the evolving need for tools that truly support developers. Observability 2.0 moves beyond monitoring operational issues, aiming to “shift left” by empowering developers from the beginning of the software development process.  

The evolution of observability 

To understand how observability is evolving and its impact on developer experience, we need to understand the tumultuous history of trying to define what observability is.  

Join LeadDev.com for free to access this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register