San Francisco, CA, USA
2011
  |  By Scott Cooper
For the last few weeks I’ve used a coding agent to find and fix backend performance issues in Sentry, starting from the traces Sentry sends to itself. Most of the fixes only changed a line or two. But together, they removed hundreds of millions of queries a week, and some expensive lookups became hundreds or thousands of times faster (more details on that below).
  |  By Markus Hintersteiner
Starting with Sentry Android SDK 8.51.0, profiling on Android 15+ devices is powered by Perfetto, through Android’s system ProfilingManager API. That means fewer legacy tracer crashes, lower CPU and memory overhead, and more representative profiles. You don’t need to change any configuration: if you already use continuous profiling, devices on Android 15 and newer pick up the new profiler as soon as you upgrade.
  |  By Abdelrahman Awad
If we were to reduce web performance into a single term, it would be “web vitals”. Web vitals are a universal signal that every developer can measure, and more importantly, optimize for. They describe many facets of the user experience when it comes to performance, but they were limited to specific types of navigations. Capturing web vitals for your apps has been largely about users landing on your site from somewhere else. We measured that experience and you optimized for it.
  |  By Anton Bjorkman
AI-powered apps are hard to debug without observability. From one run to another, AI produces different results, goes down different paths, and you’re none the wiser as to why it’s happening. Agent Tracing bridges the gap between prompt, tool calls and final output, all within the context of your app. If things break (it always does at some point, we know from experience), you get everything in one complete trace.
  |  By Armin Ulrich
This is a guest post from Armin Ulrich, a fullstack developer, and founder of placid.app. He also created the MadeWith* network where he shares his projects and allows other developers to share theirs. Two people and one beagle run the project showcase madewithvuejs.com. The beagle is actually an AI agent that we have added to our workflows, but we’re very fond of her by now. Milly is part of the team, scouting for content, building features and sniffing for bugs.
  |  By Kyle Tryon
Since Sentry added Logs and Application Metrics, there are now two ways to record that something happened in your app, and they can look pretty similar: Sentry.logger.info("user.signup") versus Sentry.metrics.count("user.signup"). Both store attributes, both include shared context automatically, and both can be filtered, grouped, and counted. So when you’re instrumenting your code, which one do you reach for?
  |  By Vlad Miricioiu
The title is not a joke. For those of you who know Sentry, you know we’ve been giving back to Open Source maintainers since our early days in whatever ways we could. But around five years ago we really started to give in a more meaningful way. This year we increased our budget from $750,000 to $1,000,000.
  |  By Nelson Osacky
Our team has been working hard over the last quarter to make sure Sentry’s Android SDK is faster for you. During this time, we reduced the Android SDK init time by 20-30%. We also reduced memory allocation, fixed memory leaks, and reduced background CPU time by up to 10%.
  |  By Gino Buenaflor
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.
  |  By Isaac Z. Schlueter
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.
  |  By Sentry
If you've never used Sentry, this is the short version. In under eight minutes, we walk through what it does, what it captures, and where to go next. Sentry is an application monitoring platform. It collects errors, logs, timings, and replays, and ties them together with tracing, so you can go from "something broke" to the line of code that broke it without opening six tabs. Here's what we cover: On data: out of the box, Sentry scrubs things like passwords, tokens, and credit card numbers. You decide what else gets collected, and you can choose US or EU storage.
  |  By Sentry
Sentry offers both "Application Metrics" and "Logs", but both can seem pretty similar. Both logs and metrics are just a collection of attributes attached to a name in your code. Both can be counted, visualized, or alerted on. Both are not sampled by default. So how do you know which to choose? In this video, we'll briefly go over a few examples of when to use logs and when to use metrics. TLDR; Logs are designed for debugging and may be temporary or likely to change when problems arise. Metrics on the other hand are stable, purposely placed events used to track user behaviors.
  |  By Sentry
Recently Warp introduced some new cloud software factories for setting up bespoke workflows and agents within your organization. The best part is that you can integrate Sentry directly into these factories. Whether you want to create an automated debugging workflow leveraging Sentry context or capture agent metrics for evals and performance data, Warp and Sentry have got it covered.
  |  By Sentry
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.
  |  By Sentry
Join Serge for an introduction to tracing and how it applies to AI agents. Through live walkthroughs, you’ll see how to follow an agent’s execution, inspect model and tool calls, and find where things went wrong. No prior tracing experience is needed.
  |  By Sentry
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.
  |  By Sentry
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.
  |  By Sentry
Welcome to HotFix, the show where Sentry customers return the favor. We helped Exa fix their code. Now, it's their turn to fix our organization.
  |  By Sentry
Checkout suddenly got a lot slower for a chunk of users, and the only clue was a spike in an application metric. In this walkthrough, we go from that spike to a linked trace that shows exactly where the time went. Using Codex alongside Sentry, we dig into the trace data, isolate the slowdown to the European backend, and follow it down to a single Stripe request that's dragging everyone down with it. Along the way, we talk through what actually helps here: caching, timeouts, async calls, and other ways to keep one slow dependency from becoming everyone's problem.
  |  By Sentry
As fast as AI can generate code, getting that code to production still tends to slow things down. It makes sense. When code breaks in production it’s not just a nuisance; it’s a full-blown incident. And can have big impacts for your company and customers. The question really is, can you catch broken code as quickly as you can ship it? In this livestream, Peter McCarron, Technical Product Marketing at Sentry, is joined by Tom Totenberg, Head of Release Automation at LaunchDarkly, to talk about how you can automatically protect new releases from code merge to error detection.

Open-source error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.

Sentry provides open source error tracking that gives you insight into every crash in your stack as it happens, with the details needed to prioritize, identify, reproduce, and fix each issue. Sentry supports all popular languages and platforms, and offers a perspective that enables you to see which errors are doing the most harm to your business and help you understand how issues affect your bottom line.

Find out about exceptions right away. Set up Sentry in minutes with just a few lines of code. Get notifications via email, SMS, or chat as part of an existing workflow when errors occur or resurface.

Quickly find and fix production errors. Triage, reproduce, and resolve errors with max efficiency and visibility. Exception handling with Sentry helps developers build better apps and iterate faster.

See the impact of each release. Integrate error tracking with your commit and deploy workflows. Aggregate events to see where bugs happen, how often, and who's affected before users even notice.

Error tracking built for community. Sentry started as and remains a 100% open-source project, now delivered as a hosted service. Development aligns to security, observability, and production at scale.

Users and logs provide clues. Sentry provides answers.