Sentry Changelog

Sentry issue alerts now support IN and NOT IN conditions for tags and attributes

We enriched the available information on the Stats page, so you can easily understand the reason events are being filtered or dropped.

Actionable hydration errors based on replay data are now available for early adopters.

We’re excited to finally announce that Session Replay is now available for mobile applications in open beta for React Native, iOS and Android. Session Replay lets developers see a visual reproduction of user engagement with their app, so you can understand when, where, and how an error is impacting your app without having to repro it yourself or talk to a customer.

We are happy to announce that the Sentry NestJS SDK is now live.

A lot of noisy errors come from JavaScript that wasn't written by yourself. Browser extensions, code-injecting browsers, or widgets from third-party services all may throw errors that you cannot address.

There are two possibilities to filter out these kinds of errors:

1. Using the allowUrls and denyUrls options
2. Using the thirdPartyErrorFilterIntegration (recommended)

Directly search for relevant traces to help debug problems

We are happy to announce that the Sentry Solid SDK is now live.

With the 8.10.0 release of our Remix SDK includes improvements to our tracing experience, and resolved a number of old issues.

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.