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.

8.6.0 of the Sentry React and Next.js SDKs add support for React 19 and its new error handling hooks. This means that Sentry will automatically attach your component stack to every new error, making it easy to know where to look in your component tree for debugging.

Sentry now integrates with OpenAI, Anthropic, LangChain, Cohere, and HuggingFace to help you monitor your LLM pipelines.

End-users can send screenshots as part of their feedback to provide more context, so you can get to the root of the problem faster.

We're excited to announce the rollout of issue priority, a new feature that helps development teams streamline their workflow by surfacing critical errors.

Sentry will now auto-detect feedback submissions likely to be spam and route them to a separate folder, which spares you from a notification while improving the quality of your inbox. You can also manually categorize feedback as spam or not spam, or opt-out of this feature.

Get Slack Thread updates as your team members take action on Sentry Issues