Operations | Monitoring | ITSM | DevOps | Cloud

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.

In this article, we’re going to look deeply at React Server Components (RSCs). They are the latest innovation in React’s ecosystem, leveraging both server-side and client-side rendering as well as streaming HTML to deliver content as fast as possible. We will get really nerdy to get a full understanding of how RFCs fit into the React picture, the level of control they offer over the rendering lifecycle of components, and what page loads look like with RFCs in place.

If you’re a developer, you need a personal website. While billionaire-owned, algorithm-based social media platforms arbitrarily decide what people should and should not see on their timelines, there’s no better time for you to carve out your own cozy corner on the web and own your content.

To the Sentry community - It was sixteen years ago that David Cramer pushed the first commit to a side project, and twelve years ago when he and Chris Jennings turned this side project into a company that exists to solve a simple problem: making debugging any software issue dead simple. Since then, we’ve been on a path slightly different from what most people consider “observability.” Sentry isn’t a platform or a company that wants to collect logs and check a monitoring box.

Sentry is pretty good at capturing all your production issues. But sometimes your user hits an issue that doesn’t fire an exception – maybe a broken link, problem with their permissions, or even something as simple as a grammatical error in copy. Sentry won’t capture those, but you should probably know about them so you can fix them.