The trace waterfall now supports time compression that shrinks empty gaps between spans, pinning an attribute to track its value across a trace from the side panel attributes tree, and clickable Web Vital pills that zoom into the point where a metric was recorded.
Sentry Changelog
npx @buildinternet/releases get sentry-changelogThree new command groups arrive: sentry feedback resolve, unresolve (alias reopen), and spam accept the same IDs, URLs, and @latest selector as feedback view; sentry replay download saves a replay by replay ID, trace ID, or URL as rrweb JSON; and sentry dsn list shows public DSNs with key name, enabled status, and creation date. A final 401 after transient retries now reports as an authentication error instead of a retry-exhaustion message.
search_events is replaced by search_errors, search_logs, search_traces, search_metrics, search_profiles, and search_replays, each searching exactly one dataset, with search_events kept as a deprecated alias on execute_sentry_tool. search_logs now runs Sentry regex filters as written, and the new find_dropped_events tool shows what Sentry received but didn't store for spans, logs, metrics, or errors, by outcome and reason.
sentry issue view and sentry issue explain now accept multiple issue IDs, sentry event view lists attachment metadata with an authenticated download URL, and a new sentry wasm-split ports Symbolicator's tool for WebAssembly build IDs and debug data. Fixed trace view for traces older than about 1.5 days, project list pagination above --limit 100, and sourcemap upload crashes on Node.js before 20.15.
Explore > Agents now supports filtering and sorting conversations on whole-conversation aggregates like conversation.totalCost, conversation.totalTokens, conversation.toolCalls, and conversation.errors, rather than only individual spans. Column headers are sortable, so conversations can be ordered by cost or errors to surface ones needing attention.
The TurboModule Context integration records calls to React Native New Architecture native modules, capturing the module and method active during native crashes, call counts, error counts, and durations per module and method on transactions and root spans, and breadcrumbs for slow asynchronous calls. It is enabled by default but wraps only the Sentry module; register your own modules via the modules option, and set enableLegacyNativeModules: true on the Old Architecture to record all registered NativeModules automatically.
Starting with Sentry Android SDK 8.60.0, SentryNavEffect used alongside NavDisplay records navigation transactions, breadcrumbs, screen names, and back stack context via SentryNavOptions. The initial release is experimental and covers single-stack apps, adding back stack context to what the Nav2 integration already produced.
The SDK now captures native crashes such as segmentation faults as minidumps and sends them to Sentry on Linux, macOS, and Windows, covering crashes in unsafe code and FFI calls into C libraries that occur without a panic. Enabled by compiling the sentry crate with the minidump feature and adding MinidumpIntegration at init.
Sentry Logs search now supports regular expressions, letting you filter any string attribute by pattern rather than exact text via a "matches regex" operator in Explore → Logs. Patterns use RE2 syntax, are case-sensitive by default, and are capped at 64 characters.
Automatic agent tracing across Node.js, Bun, Cloudflare, and Deno now covers additional AI frameworks and providers including eve, Mastra, Flue, Pi Durable, Groq, Together AI, and Mistral AI, with the default mcpServerIntegration replacing the need to call wrapMcpServerWithSentry. Classifiers such as Jev produce gen_ai.evaluate spans via typesafeIntegration, and handled errors no longer generate error reports in the OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph integrations.
An experimental Memory Limiter integration for the Sentry Android SDK turns Android 17's silent app terminations over memory budgets into reportable Sentry events. It is disabled by default and requires Sentry Android SDK 8.57.0 or later, Android 17 (API level 37), and an SDK cache directory; enable it via the io.sentry.memory-limiter.enable manifest meta-data or options.isMemoryLimiterEnabled.
Sentry now integrates with Origin, providing stack trace linking that jumps from a stack frame to the exact line in Origin, CODEOWNERS import for email-based ownership rules, release commit tracking, and issue resolution via fix references in commit messages and PR descriptions. Connecting one Origin account to multiple Sentry organizations requires a Business or Enterprise plan.
The hosted Sentry MCP server can now create, update, and delete alert rules and metric monitors, and a new link_issue tool attaches Jira, GitHub, GitLab, Bitbucket, Azure DevOps, or Sentry App tickets and GitHub pull requests to Sentry issues by URL. Writes require the Manage Projects & Teams skill, and existing connections must re-authorize to grant the new alerts:write OAuth scope.
Seer Agent can now write to Sentry through the Sentry API, setting up custom dashboards and widgets, creating monitors and alerts, assigning, resolving, and archiving issues, and saving explore queries and issue views, using the user's existing permissions with write-scope confirmation per action. Seer Connectors also pull infrastructure data from Datadog and Google Cloud Platform via API keys, not OAuth, alongside Sentry data.
When creating or editing an alert, the "Alert on all issues in all projects" source makes a single alert trigger on issues from any project, including new and future projects, so the project list no longer needs manual updates. It covers any issue from any monitor, including uptime failures, cron misses, errors, and metric thresholds; all admins and managers can create these alerts.
Version 11.0.0 of the Sentry JavaScript SDK is now available. The goal of this release is to be better compatible with OpenTelemetry, make our integrations work across Node.js, Cloudflare, Bun and Deno through run-time and build-time instrumentation, and make span streaming and…
Seer can now push follow-up commits to pull requests it opened instead of requiring a re-run of Autofix for a brand-new PR, taking feedback from the Sentry Autofix panel, GitHub comments starting with @sentry, and review comments from humans or bots. It also investigates failing CI checks and pushes fixes, with automatic attempts capped. PR iteration works with GitHub only.
Agent Tracing captures model calls, tool executions, sub-agent handoffs, token usage, and cost as spans inside existing Sentry traces, with conversation IDs exposing the full message exchange between agents and users. Alongside GA, the overview gains readable conversation titles and charts of cost, conversation count, and total messages over time, and the timeline and transcript views now show tool calls inline with input previews and durations.
Logs and metrics are now enabled by default, with enable_logs and enable_metrics removed; OTLP trace export and propagator default to false. New granular data_collection config replaces the deprecated send_default_pii, and Rails breadcrumbs now respect these controls.




