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.

The JavaScript SDKs now trace more AI frameworks, providers, and classifiers across Node.js, Bun, Cloudflare, and Deno, with more consistent data in traces.

You can now forward logs/traces from Vercel automatically via the Vercel Marketplace Integration

You can send Metrics to Sentry using our PHP, Laravel and Symfony SDKs

UI Profiling is now supported in the Sentry Browser JavaScript and Electron SDKs

You can now forward logs from the OpenTelemetry Collector, Vector, or Fluent Bit to Sentry

Code Review is now in beta for organizations using Sentry’s EU data region. Try it for free.

We just launched our Cursor Cloud Agent integration. Now when Seer finds a bug, it can hand it off to Cursor—replete with all the context Sentry has about the issue—to write the fix and create a PR for you.

We are changing the list of IP addresses that are used for event ingestion

Send counters, gauges, and distributions from your code to track things like email.sent, checkout.failed, queue.depth etc — and pivot directly into the related traces, logs, and errors when something looks off.

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

You can now forward logs from platforms like Cloudflare, Vercel, Heroku, and Supabase to Sentry