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.