Fingerprint rules let you override how Sentry groups errors into issues. We shipped a few fixes that make rules easier to write and debug, whether you write them yourself or ask Seer Agent to.

You can connect Seer Agent to your Grafana account and let Seer correlate your errors,traces,logs etc in Sentry to the relevant telemetry in Grafana

Sentry Go SDK v1 redesigns the API around Go's context, removing hubs. Try the alpha and share feedback before the stable release.

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

Agents using Sentry MCP can now tell configured drops from lost data, choose the right attribute in projects with many fields, and wait less on project-scoped connections.

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.

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.

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.

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.

End-users can submit bug reports anytime with the new widget, and Sentry will then link that to available rich debugging context, including replays, errors, and tags such as URL, so you can get to the root of the problem faster.

If you're using React and having a hard time deciphering CSS selectors, use our new component name plugin.

Are users smashing buttons on your site expecting something to happen? Now you can get alerted to rage clicks within Sentry to take action on them as soon as they occur. With rage click issues, you can get all the handy workflow components that come with Sentry issues to triage your rage clicks (i.e., resolve, assign, archive, etc.) as well as the debugging context needed to resolve them.

Replays have always been a crucial part of the debugging workflow, but required leaving the issue in order to do so. Now embedded directly within the issue details page, Replay clips offer a way to save you precious time and context switching.

Identify signs of user frustration with rage click issues in Sentry - a series of rapid clicks on an the same unresponsive element.

We're excited to announce canvas support is now available in beta for Session Replay videos. For all websites/apps that leverage HTML canvas elements, you...

If you’re using Next.js with Sentry’s Session Replay, we’ve launched an experimental Hydration Error diff tool.