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.

No action is needed for most users. In this release, Sentry’s published internal JavaScript packages moved from @sentry-internal/* to @sentry/*, and the SDK now depends on the new package names automatically.

A regression in data scrubbing prevented specific attributes from being scrubbed

Replay filters (events, tags, URLs, CSS selectors, etc.) can now be saved and reused later.

We’ve made a few changes to make replays easier to use and share.

Replay summaries, now available for early adopter let you quickly understand what happened in user sessions without having to watch the entire replay. Each summary provides a clear narrative and structured chapters, allowing you to jump straight to important moments and debug faster.

We've updated Sentry Docs to better reflect the Event fields we apply data scrubbing by default when using our Require Using Default Scrubbers feature.

The tree compare tool helps diagnose hydration errors in React by identifying and time stamping DOM mutations, with detailed context for debugging.

See the differences between client-rendered and server-rendered HTML when hydration occurs on your app to debug the problem faster and improve your site's web performance.

Replay now has Web Vital breadcrumbs, which show the Web Vital score as well as the elements contributing to that score.

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