The data you need to monitor AI-powered applications differs from other parts of your tech stack. Whether you need to debug an error, improve performance, or better understand costs, the context you need for an app calling a large language model (LLM) is different from an app that isn’t.

You’re seeing an unusually high number of 429 status codes, but your monitoring solution can’t tell you much beyond that. Typically, that’s when you start searching through logs — while simultaneously sustaining the urge to walk away and hope someone else deals with it. To make sure neither of those happens, we made a new set of debugging workflows aptly named Insights.

Largest Contentful Paint (LCP) is a Core Web Vital (CWV) metric that marks the point in the page load timeline where the main page content has likely finished loading. To get a good LCP score, the main content on a web page must finish loading in under 2.5 seconds.

Dan Mindru is a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CrontTool. “Hey, can you give me the steps to repro?” This is the message I never want to send but end up sending way too often. And the answer?

As first announced during Sentry Launch Week, we have been working on shipping a major release of our JavaScript SDKs. This update makes getting started with Sentry JavaScript SDKs (even more) straightforward. This release broadens the number of frameworks and libraries where we provide automatic instrumentation, meaning you can access telemetry data in Sentry on day one, without configuration.

Google Lighthouse has been one of the most effective ways to gamify and promote web page performance among developers. Using Lighthouse, we can assess web pages based on overall performance, accessibility, SEO, and what Google considers “best practices”, all with the click of a button. We might use these tests to evaluate out-of-the-box performance for front-end frameworks or to celebrate performance improvements gained by some diligent refactoring.

The term “observability” is a strange one. We understand its value as a way to describe a sophisticated approach to monitoring complex distributed systems and microservices. But the term is inherently passive (and let’s be honest. It’s a bit of a loaded marketing term). Simply “observing” doesn’t help you solve problems – especially if you are inundated with loads of non-actionable data.

In case you missed it, our friends at Laravel just announced a new partnership with… well… Sentry. The TL;DR is that you can add error monitoring and tracing capabilities to new or existing Forge/Vapor sites with just a few clicks. This new integration is designed to help PHP developers collect real telemetry on their projects as easily as possible.

We recently added the User Feedback Widget to the Sentry platform, and now we are releasing two additional features to the product to help developers get deeper context into bug reports without being inundated with them: user-generated screenshots and automatic spam detection.

Sentry recently completed a multi-month project to remove all non-essential cookies and trackers from our public websites. For more context, see two blog posts that offer differing perspectives on the project: one from our marketing team, another from our legal team, and a third blog post that explains our privacy values and our ultimate motivation.