Software architectures are greatly influenced by the size and scale of the software applications. With growing size, the code base becomes complex. With scale, the deployment becomes challenging. The result: debugging becomes an increasingly time-consuming process for developers.

There’s an increasingly high cost to poor data quality today. Poor customer data costs companies six percent of their total sales, as per a UK Royal Mail study. And, as per IBM, bad data costs U.S. businesses $3.1 trillion per year. As companies transform into data-driven businesses, we witness a sharp interest in data observability.

The modern standard for observability in backend systems is: distributed traces with OpenTelemetry, plus dynamic aggregations over these events. This works very well in the world of web servers. But what about the web client? This post describes the state of OpenTelemetry support for React web clients, as of early April 2023.

As technology advances, so does the need for software engineers and DevOps teams to understand the precise inner workings of the systems they create. In 2023, observability is quickly becoming a key factor in gaining success for many businesses. The study states that many businesses are in different stages of adopting observability into their arsenal of tools, and that the need for these practices is on the rise.

To say modern enterprises are built on the cloud is an understatement. According to Gartner, enterprise spending on cloud applications surged to 57.7% in 2022, and investments into public cloud services hit a respectable 41%. These numbers are only predicted to grow further in 2025 as enterprises accelerate cloud rollouts and move into a cloud microservices architecture to realize greater agility, productivity, and competitiveness.

At a recent training session, Jeli spent a great deal of time covering incident retrospectives and what makes an incident worthy of studying. My colleague Ben Hartshorne asked a fascinating question, which I’ll paraphrase here: That caught me by surprise. We had a great discussion, and it made me consider approaches I hadn’t before.