Operations | Monitoring | ITSM | DevOps | Cloud

To create exceptional products, developers need to understand the behavior of backed systems; however, we generally have the most control over the applications we’re deploying (not their dependent infrastructure). With this in mind, we’ve added new Insights to Sentry, providing visibility into common backend building blocks such as Caches, Queues, Queries, and Outbound Requests so you can quickly troubleshoot and debug issues when they occur.

The internet is basically just a bunch of websites calling each other. You make a call to some service, that service calls you back, and then that service goes down and ruins your afternoon. Requests, our latest addition to Insights, is a place to see, understand, track, and improve the behavior of outgoing HTTP requests.

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?