---
title: "Sentry"
description: "11 posts about Sentry, summarised, each linking to the original."
---

# Sentry
> 11 posts about Sentry, summarised, each linking to the original.

## Articles

### [Sentry's Flutter SDK 10.0: Streaming Traces and More Accurate Crash-Free Rates](https://yomu.fyi/post/sentry-s-flutter-sdk-10-0-streaming-traces-and-more-accurate-crash-fre.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Gino Buenaflor
- Published: Oct 14, 2026
- Type: Announcement

Sentry released Flutter SDK 10.0, making streaming traces the default so spans reach Sentry as they finish, using Sentry.startSpan for custom work. Unhandled Flutter errors no longer mark the session as crashed, improving crash-free rate accuracy by keeping the session running until a real crash occurs. App startup on Android and iOS now has its own trace with breakdowns such as root-widget attachment and first-frame rasterization, and can be extended with SentryFlutter.extendAppStart. The release simplifies logs and metrics setup by removing separate enable flags, expands Dio network error capture to failures without HTTP responses, and respects Flutter’s SensitiveContent widgets in Replay and screenshots. Upgrading requires Dart 3.12, Flutter 3.44, Android API 26, and iOS 15, with native SDK installation via Swift Package Manager on iOS and macOS.


### [Sentry JavaScript SDK v11 adds tracing for all JS platforms](https://yomu.fyi/post/sentry-javascript-sdk-v11-adds-tracing-for-all-js-platforms.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Isaac Z. Schlueter
- Published: Oct 9, 2026
- Type: Announcement

Sentry JavaScript SDK v11 replaces OpenTelemetry-based tracing with a code transformer from the apm-js-collab packages that injects diagnostics channels into supported modules at load time. The transform wraps target functions in tracingChannel() calls, and Sentry integrations subscribe to those channels to create native spans directly from the events. This approach works both at runtime via Module.registerHooks and at build time through bundler plugins for Vite, esbuild, webpack, and others, with no risk of double-wrapping. The previous OpenTelemetry instrumentation required Node-specific loader hooks, could not instrument bundled dependencies, and had ordering issues with ESM imports, limiting support to Node.js. v11 extends automatic tracing to Cloudflare Workers, Deno, Bun, and bundled server deployments while offering three OpenTelemetry integration modes: Sentry only, OpenTelemetry-compatible, or custom OTel with OTLP export.


### [Reducing Android scope-sync overhead in Sentry Flutter](https://yomu.fyi/post/reducing-android-scope-sync-overhead-in-sentry-flutter.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Gino Buenaflor
- Published: Oct 8, 2026
- Type: Problem & solution

The Sentry Flutter SDK records breadcrumbs, user information, and diagnostic data through scope updates, adding overhead to apps. On Android, a dedicated worker isolate handles Sentry Android SDK operations to avoid blocking the main UI isolate, but both the calling isolate and the worker normalized the same data, and the encoding step produced a JSON string plus an unnecessary byte buffer copy. Removing the duplicate normalization roughly halved normalization time, while using JsonUtf8Encoder to encode directly into UTF-8 bytes reduced encoding time by 16% and eliminated the extra copy. Combined, these changes reduced total scope payload processing time by 27–30% for benchmark inputs of 1.2 KB, 23 KB, and 238 KB, as measured on a Google Pixel 4 in release mode. The optimizations are available in sentry\_flutter version 9.26.0 and later.


### [Unreal MCP now speaks Sentry](https://yomu.fyi/post/unreal-mcp-now-speaks-sentry.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Ivan Tustanivskyi
- Published: Oct 6, 2026
- Type: Announcement

Unreal Engine 5.8 introduces Unreal MCP, an experimental feature that runs a first-party MCP server inside the editor, allowing coding agents to drive the editor directly. The Sentry plugin registers tools and skills that agents can use to set up crash reporting, including DSN configuration, symbol upload, instrumentation, and crash debugging. Agents can discover and use these tools through the editor’s MCP interface, with skills that follow ground rules like asking before changing settings and never exposing secrets. The integration also supports connecting to Sentry MCP for server-side operations like fetching DSNs and looking up events. In a test with the Sentry Tower demo, an agent configured Sentry from scratch, enabled symbol upload, packaged a build, captured a crash, and identified the root cause as an empty projectile class in a level-up button.


### [Seer, the Sentry MCP and CLI, or your own coding agent: where each one fits](https://yomu.fyi/post/seer-the-sentry-mcp-and-cli-or-your-own-coding-agent-where-each-one-fi.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Paul Jaffre
- Published: Oct 2, 2026
- Type: Explainer

Seer is Sentry’s agent debugger that reasons across errors, traces, logs, profiles, and linked repositories to identify root causes, not just surface-level stack traces. The Sentry MCP, set up via the agent plugin with a single command, bridges Sentry’s data into coding agents like Claude Code and Cursor, enabling them to invoke Seer’s full analysis. The new Sentry CLI provides natural-language access to Seer’s diagnosis and issue management directly from the terminal, using selectors like @latest and @most\_frequent. These tools are complementary: Seer provides deep diagnosis, while the MCP and CLI deliver that context into the environments developers already use. Teams can automate the entire workflow so Seer diagnoses, an agent fixes, and a draft PR awaits review without human involvement until approval, with Seer triggering on issues meeting event count and fixability thresholds.


### [How Etsy gets its mobile apps ready for peak traffic](https://yomu.fyi/post/how-etsy-gets-its-mobile-apps-ready-for-peak-traffic.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Sergiy Dybskiy
- Published: Sep 30, 2026
- Type: Explainer

Mobile apps cannot be reverted after release, so Etsy’s peak traffic preparation focuses on observability and mitigation decisions made months in advance rather than capacity scaling during the event. The company runs a code slush with three phases: mindful merging in mid-October, infrastructure fortification, and peak requiring senior sign-off for any change. To avoid tooling disruption, Etsy ran both legacy and new crash reporters simultaneously through a dual-reporting layer, letting engineers use the tool they knew and providing comparison data to eventually sunset the old platform. Before peak, each crash-prone feature is ensured to have a remote flag that disables the failing code path without an app store release. Crash rate is translated into an estimate of lost orders via business analysts, making technical health discussable with teams and the CTO.


### [Big improvements to Seer Agent](https://yomu.fyi/post/big-improvements-to-seer-agent.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Peter McCarron
- Published: Sep 29, 2026
- Type: Announcement

Seer Agent, Sentry’s AI debugging assistant, now performs write actions through the Sentry API, such as setting up custom dashboards, creating monitors and alerts, and assigning, resolving, and archiving issues. It defaults to the user’s permission level and explicitly requests permission for tasks outside its write scope, with permissions not persisting beyond a single chat. The agent can also incorporate infrastructure data from external monitoring platforms like Datadog and Google Cloud Platform via Seer Connectors, using API keys instead of OAuth. This allows Seer Agent to diagnose issues by connecting front-end and back-end data beyond Sentry’s native scope. These updates evolve Seer Agent from a conversational rubber duck into a proactive debugging assistant that can act on behalf of users.


### [Measuring the back/forward cache with Application Metrics](https://yomu.fyi/post/measuring-the-back-forward-cache-with-application-metrics.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Abdelrahman Awad
- Published: Sep 24, 2026
- Type: Announcement

The back/forward cache (bfcache) allows instant page restores by freezing snapshots, yet its hits register no events in traditional telemetry, creating a blind spot for teams. Sentry’s bfcacheMetricsIntegration fills this gap by modeling three browser-provided signals as application metrics: a navigation counter with hit/miss outcome, a per-reason counter for misses via the notRestoredReasons API, and a distribution of fallback reload duration. The integration is opt-in and launched in JavaScript SDKs v11; detailed miss reasons are currently Chromium-only due to browser API support. Users can query these metrics to break down bfcache health by route, release, or browser, enabling discovery of regressions caused by unload listeners, cache-control headers, or third-party scripts. This turns the bfcache from an invisible performance feature into a measurable, trackable signal that teams can monitor and improve.


### [Building Sentry's Laravel AI Integration](https://yomu.fyi/post/building-sentry-s-laravel-ai-integration.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Martin Linzmayer
- Published: Sep 21, 2026
- Type: Announcement

Sentry’s Laravel AI integration, built during an internal Agent Hackweek, provides Agent Tracing for Laravel AI agents. The author used Claude for coding, which initially produced poor generic helper code. Laravel AI emits lifecycle events for agents and tool calls, but not for individual LLM invocations. To capture these, the integration matches outgoing HTTP requests to active invocations using provider URL prefixes, associating with the most recently started invocation if multiple match. Enabling the integration requires only updating to sentry-laravel 4.27, with no Sentry-specific code. Traces appear in Sentry’s Explore > Agents section, showing conversations, tool calls, and their inputs and outputs.


### [Debugging our AI search assistant with agent tracing](https://yomu.fyi/post/debugging-our-ai-search-assistant-with-agent-tracing.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: Dominik Buszowiecki, Shaun Kaasten
- Published: Sep 11, 2026
- Type: Explainer

Sentry’s Search Query Assistant converts natural-language prompts into Sentry Search Syntax, but its non-deterministic output requires evals and debugging when generated queries are wrong. A production issue caused searches on custom numerical attributes to return no events, so the team used Sentry’s AI Conversation view and Agents filters to find the relevant trace, inspect the timeline, and follow tool calls into the backend API. The trace showed that tool results were being incorporated into the system prompt with the field name bug\_\_predictions\_count instead of the required tags\[bug\_predictions\_count, number\] form. The team added an eval scenario, fixed the prompt generation, verified the corrected query locally and in production, and confirmed the updated prompt and API parameter in the trace. They also instrumented local eval runs to send data to Sentry, allowing debugging before a pull request.


### [Automated Sentry Error Tracking](https://yomu.fyi/post/automated-sentry-error-tracking.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Sep 12, 2023
- Type: Announcement

Fly.io announces Sentry as the default error-monitoring tool for its applications, with new deployments receiving an automatically provisioned Sentry project and existing apps using flyctl ext sentry create. Each organization receives one year of monthly Team Plan credits covering 50,000 error events, 100,000 performance units, 500 session replays, and 1GB of attachment storage. For Rails apps, flyctl launch installs the required gems, creates initializers, and sets the SENTRY\_DSN secret, allowing boot failures, memory exhaustion, exceptions, latency issues, and crashes to reach Sentry. The post demonstrates a deliberately raised Ruby exception, then uses flyctl apps errors to open the Sentry issue dashboard and identify the bug; planned extensions include release tracking and out-of-memory events.
