Operations | Monitoring | ITSM | DevOps | Cloud

Sentry's Flutter SDK 10.0: Streaming Traces and More Accurate Crash-Free Rates

Sentry’s Flutter SDK 10.0 makes streaming traces the default and changes how unhandled Flutter errors affect Release Health. Errors that leave your app running no longer mark the session as crashed, so your crash-free rate better reflects actual app crashes. The release also gives app startup its own trace on Android and iOS, simplifies logs and metrics setup, expands Dio network error capture, and respects Flutter’s sensitive-content markings in Replay and screenshots.

Sentry JavaScript SDK v11 adds tracing for all JS platforms

This post is about a recent change to the Sentry JavaScript SDKs. If you don’t use Sentry with JavaScript, it may still be useful as a look at how we made the change and why. In the Sentry JavaScript SDK v11, we rebuilt how our tracing integrations work. While we still support the OpenTelemetry standard (described in more detail below), we now instrument your dependencies with a code transformer instead of using the OpenTelemetry instrumentation classes as we did in previous versions.

Fixing 3 issues with one distributed trace

Use Sentry tracing to investigate three different problems in one shopping flow: an N+1 query, an expired promo-code warning, and a checkout exception. The entire shopping flow happens through the agent conversation on Empower Plant’s homepage: a search for plants under $200, adding one of each to the cart, starting checkout, applying SAVE20, then attempting to place the order. The trace connects that flow to repeated database queries and an N+1 issue, a warning that SAVE20 has expired, and a checkout exception with its inventory-validation stack trace.

Reducing Android scope-sync overhead in Sentry Flutter

Our SDK adds work to the app that installs it. It records recent app activity as breadcrumbs and keeps user information and other diagnostic data up to date. Changes to that information are called scope updates. On Android, we send those updates to a worker isolate, which passes them to the Sentry Android SDK. We found that the calling isolate and the worker both normalized the same data. The encoding step also created a JSON string and an extra byte buffer that we could avoid.

Searching Sentry Logs with Regex

We use Sentry's new Regex search for Logs to hunt for non-obvious bugs in our app. What do you do when traces show that Postgres jobs are backing up? Logs are trace-connected, so by looking at one of the affected traces, we can see all of the logs on that trace. In there, we can see Postgres has logged that it acquired a lock only after a long wait. Using regex, we can find all of these logs that describe acquiring a lock after a 10-second-plus wait. That narrows our search from thousands or hundreds of logs down to about a dozen.

Seer Agent: Get Answers. Take Action.

This video walks through what it looks like to treat Sentry's Seer agent the way you already treat a chatbot, asking it plain language questions about your own production application. From Slack or inside your Sentry account, Seer Agent can answer questions with real context: the affected spans, the recent release, the likely cause. Seer doesn't stop at answering questions. Ask it to act on what it just told you and it completes that work inside Sentry, serving as an assistant to your projects, team workflows, and your future self.

Unreal MCP now speaks Sentry

Setting up crash reporting is rarely the most exciting part of shipping a game. Paste a DSN, flip a few checkboxes in Project Settings, turn on symbol upload, package a build, crash it on purpose and check that the event shows up in Sentry… It’s not hard to do (and important), but it’s the kind of work you’d happily hand off to someone else. With Unreal Engine 5.8, that someone else can be your coding agent.

Seer, the Sentry MCP and CLI, or your own coding agent: where each one fits

I’ve been getting some version of this question a lot lately, mostly in our Seer preview webinars. Different audiences, same handful of questions: Worth answering all three in one place. Honestly, I needed to write this down for myself too. Things are moving fast around all of us and answers seem to get more nuanced by the week. This is an attempt to codify the difference: what each option is and when it makes sense to reach for one over the other.