I always tell people "Observability is not logs, metrics, and traces! Observability is empowering your team to ask questions." That's very aspirational and sounds good, but it's not at all clear. I now have a self-contained story that perfectly explains it!

When a startup is in its very early stages, rapid iteration and dynamism are at the top of its priorities. The ability to do so, while maintaining a stable and high-quality product, is a big challenge facing the R&D group. We want to release features as quickly as possible, but this rapid velocity cane cause conflicts when writing in-depth, comprehensive tests.

Losing track of communication between applications or code has become a problem with the tech world growing more into supporting Serverless cloud architectures and allowing the developer to maintain, upgrade and update these services. One might say that services and code are becoming more loosely coupled, allowing code to run and execute in silos. Let's take an AWS Lambda function as an example.

Debugging JavaScript is an inevitable part of web development, and not the nicest one. Debugging jobs always seem to pop up when you’re already buried under piles of work, and a teammate pings you about an issue that was overlooked in testing and has been causing frustrations since your last release. That’s why it helps to be prepared for that eventuality, and equipped with the developer tools to help you debug faster.

I was intrigued by two recent IoT related survey and reports. They emphasize use cases about efficiencies and return on investments but, surprisingly, there is no mention of people-safety nor productivity. I think it is imperative to place people at the heart of the IoT universe. Today, people related use cases have been greatly understated. We will be doing a great injustice if we continue to ignore the human angle.

Payment gateway outages and performance issues have a disruptive effect on your business. When customers cannot complete a transaction, it leaves them frustrated and anxious. Even if it is not an outright outage, customers are wary of a flaky payment experience. They are often reluctant to retry the transaction for fear of being charged twice. This results in abandoned purchases and lost revenue.

Kubernetes 1.24 is about to be released, and it comes packed with novelties! Where do we begin? Update: Kubernetes 1.24 release date has been moved to May 3rd(from April 19th). This release brings 46 enhancements, on par with the 45 in Kubernetes 1.23, and the 56 in Kubernetes 1.22. Of those 46 enhancements, 13 are graduating to Stable, 14 are existing features that keep improving, 13 are completely new, and 6 are deprecated features.

As most developers know, alert-fatigue is real, and the last thing you want is another feed of notifications. Read on to learn how the new Alert Details view helps you filter out notifications for Issue Alerts you don’t care about, and how it can help you focus on the ones that do. When you get started with Sentry, you’ll likely create an Alert for every Issue.