Four years ago, we stepped on some big toes with our developer-first performance monitoring. Since then thousands of software teams have adopted our modern APM solution. But while Performance checks off a lot of boxes, some dev teams juggle separate tools for metrics, leading to a fractured experience. And honestly, what good is a metric without all the context you get from Sentry? Not very – it makes tying problems back to underlying errors or performance issues unnecessarily difficult.

With the release of.NET 8, Microsoft released a new framework called.NET Aspire that’s shaking up the way distributed applications are crafted. Aspire makes it painless to configure and deploy distributed apps in.NET. You can check out the Aspire docs for a full rundown.

On March 12th 2024, Google is launching a new Core Web Vital metric, Interaction to Next Paint (INP). INP will replace First Input Delay (FID) and will change the way your sites are assessed for performance by Google, which ultimately affects how your sites rank in search engine results. TL;DR: You need to start optimizing for INP today so your sites are not negatively impacted after March 12th.

Based on our experience working with thousands of mobile developer teams, we developed a mobile monitoring maturity curve here at Sentry. We hypothesized that once teams achieved stability and were no longer firefighting and fixing crashes, they’d shift to streamlining workflows and eventually focus more on optimizing mobile app performance. In a recent workshop, we asked mobile devs where they fell on the curve. The results were surprising.