The JavaScript SDKs now instrument Cloudflare Clairic, and send events through a tunnel path derived from your DSN.

The trace waterfall now includes time compression, pinned attributes, and clickable Web Vital pills to help you focus on the parts of a trace you want to investigate.

Resolve, reopen, or mark User Feedback as spam, download Session Replays as rrweb JSON, and list a project's DSNs from the Sentry CLI.

View or explain several issues at once, see event attachments, and split WebAssembly debug data from the Sentry CLI. Older traces and large project lists no longer fail.

Agents using Sentry MCP now search each dataset with a dedicated tool, can see which events Sentry dropped and why, search logs with regular expressions, and open dashboards from a URL.

You can now filter and sort conversations in Explore > Agents on totals like cost, token count, tool calls, and errors.

The React Native SDK now records the calls, duration, and errors of native modules, and adds the active call to crash reports.

The Android SDK can now instrument Nav3 back stacks to capture navigation transactions, breadcrumbs, screen names, and more.

The Rust SDK can now report native crashes, such as segfaults in unsafe code, to Sentry.

Sentry Logs search now supports regular expressions (regex), so that you can search log lines that match a pattern, not just by the exact text.

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.

PHP developers working with wordpress have been able to integrate Sentry into their application for error monitoring using a community maintained integration. With the latest release it now supports tracing and profiling as well.

Check out the latest release v7.17.0 to try it out,

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.