|
By Rahul Chhabria
You already have everything you need. If you’re using Sentry, you have traces, structured logs, and now application metrics. Most teams use that stuff for debugging and stop there. But get this: that same data can answer most of the product questions you’ve been sending to a separate analytics tool, maintained by a separate team, with a separate data model and a separate bill. (Not all of them.
|
By Ben Coe
The traditional dashboard workflow, teams slowly handcrafting visualizations to track critical KPIs, is dying in a world of AI agents. A few years ago, in a pre-agentic-everything world, we tried to make it easier for developers to monitor critical experiences. We introduced Insights pages, which were pre-configured dashboards any Sentry user could adopt instantly that surfaced common health signals, like Web and Mobile Vitals.
|
By Sergiy Dybskiy
The way we build software has drastically changed over the past few years. What hasn’t changed is that this software ends up in front of real people: you, me, my mom. And when those users inevitably run into something broken, you as the application’s developer need to be equipped with the right tools, context and understanding of what broke, where it broke, and how to fix it as quickly as possible. Every day we’re inching closer to self-healing software.
|
By Ivan Tustanivskyi
Your Unreal game can ship with zero errors and still not feel great. Stutters during combat, a frame-rate cliff on the big boss, rubber-banding in multiplayer, none of it shows up as a crash and none of it shows up in Sentry, leaving you without any visibility into what your players are actually experiencing in the wild. Well, until now. Unreal Engine already gives you plenty of tools to measure game performance and collect runtime stats, but all that data stays on the dev’s machine.
|
By Abdelrahman Awad
Over the past few weeks, we have been driving a cross-ecosystem effort to replace the “monkey-patching” that powers all JavaScript APM tools today with something built into the runtime. Here is why, how, and where it stands. This applies to server-side JavaScript only (Node.js, Bun, Deno, Cloudflare Workers). Browsers do not have diagnostics_channel and lack the async context propagation primitives needed to polyfill it.
|
By Aleksandr Pantiukhov
Events from Expo apps account for about 75% of the total event volume we receive from React Native apps. That number made it an easy decision to invest in updates to the Sentry React Native SDK to improve the debugging and performance workflow for your Expo apps. With these updates, you can now.
|
By Ben Coe
A few weeks ago we had a bug with Session Replay. Replays were failing in some browsers once more than 1,000 video segments loaded. We had no idea how often it happened or who was hitting it, and because the failure didn’t always produce an error, we had no way to find affected users to reproduce it. Before, we could’ve answered this with spans or logs, but it’s clunky — spans are often sampled, so you can miss outliers; logs are less structured and tend to change over time.
|
By Amir Mujacic
If you work in game development, VFX, or any industry dealing with large binary assets, chances are your codebase lives in Perforce P4. It’s the version control system behind some of the biggest games and creative projects in the world — and until now, it’s been one of the last major SCMs without first-class Sentry support. Today, we’re changing that. The Sentry + Perforce P4 integration is now generally available for all Sentry organizations.
|
By Burak Yiğit Kaya
Two commands. That’s how little it takes to go from nothing to a fully configured Sentry project with error monitoring, performance tracing, and session replay: Click to Copy No signup form. No email verification dance. No dashboard tab-switching to copy-paste a DSN into your.env. Your account is created, your project is provisioned, and five environment variables land in your working directory, ready for your SDK to pick up. And if you’re using a coding agent?
|
By Rahul Chhabria
This is a story about an engineer’s night that could have been bad, but ended up… not so bad. A few weeks ago, on a Saturday, our AI debugger, Seer, started failing. Note the big scary spike on the right. The errors were generic failures from the LLM calls, nothing that pointed at a root cause. Most of the team wasn’t scheduled to be on this weekend, and it just so happened Indragie, our Head of AI, was online. He started paging engineers.
|
By Sentry
Next.js applications can be challenging to debug in production. It’s not always clear where an issue originated or how it impacts users. Hydration errors, server component failures, and performance bottlenecks don’t always come with clear answers.
|
By Sentry
In this workshop, Paul Jaffre will show you how to query Sentry’s telemetry using natural language with Seer Agent.
|
By Sentry
Sentry already alerts your team in Slack, but with Seer, you can investigate and fix issues without ever leaving. It's like having the Sentry MCP server living right in your Slack channel. See how the Seer Agent (now in open beta!) and actionable alert messages turn your Slack channel into a debugging workflow.
|
By Sentry
XcodeBuildMCP gives AI agents the ability to build, test, and debug native iOS and macOS apps. In this hands-on workshop, we show you how to use the open source MCP server to unlock the full developer loop — build, run, debug, interact, and verify — without leaving your preferred AI coding environment.
|
By Sentry
In this workshop, we’ll show you how to use Sentry Agent Monitoring to crack open the black box that is AI — inputs and outputs, token usage, model performance — so you actually know what the robots in your application are doing.
|
By Sentry
We've officially launched Application Metrics! In this video @nikolovlazar is introducing you to them and is showing you how to use them. Each plan gets 5GB of Application Metrics for free. Chapters.
|
By Sentry
We just launched Application Metrics! Track the signals you care about, and when something spikes, click straight into the trace, logs, and errors that caused it. No more guesswork. Counters, gauges, and distributions. One line of code. Full trace context.
|
By Sentry
Welcome to HotFix, the show where Sentry customers return the favor. We helped Bolt fix their broken code. Now, it's their turn to fix something for us. Featuring Bolt Co-Founders, Eric Simons and Albert Pai.
|
By Sentry
In this live session, we’ll take a Supabase app and instrument it end-to-end — so when something breaks, you can trace it back to the exact layer, whether that’s an edge function, a slow query, or auth, and get AI-powered root cause analysis, and know what to patch and why.
|
By Sentry
We've published Sentry pre-built dashboards that are free and extensible! Check them out!
- May 2026 (15)
- April 2026 (32)
- March 2026 (12)
- February 2026 (11)
- January 2026 (24)
- December 2025 (10)
- November 2025 (15)
- October 2025 (8)
- September 2025 (21)
- August 2025 (13)
- July 2025 (12)
- June 2025 (15)
- May 2025 (18)
- April 2025 (15)
- March 2025 (14)
- February 2025 (17)
- January 2025 (9)
- December 2024 (13)
- November 2024 (15)
- October 2024 (9)
- September 2024 (11)
- August 2024 (21)
- July 2024 (19)
- June 2024 (10)
- May 2024 (11)
- April 2024 (9)
- March 2024 (23)
- February 2024 (6)
- January 2024 (11)
- December 2023 (12)
- November 2023 (15)
- October 2023 (7)
- September 2023 (14)
- August 2023 (7)
- July 2023 (11)
- June 2023 (10)
- May 2023 (9)
- April 2023 (7)
- March 2023 (13)
- February 2023 (15)
- January 2023 (8)
- December 2022 (13)
- November 2022 (10)
- October 2022 (11)
- September 2022 (16)
- August 2022 (13)
- July 2022 (18)
- June 2022 (12)
- May 2022 (19)
- April 2022 (13)
- March 2022 (11)
- February 2022 (16)
- January 2022 (2)
- December 2021 (7)
- November 2021 (9)
- October 2021 (5)
- September 2021 (12)
- August 2021 (10)
- July 2021 (6)
- June 2021 (9)
- May 2021 (14)
- April 2021 (9)
- March 2021 (8)
- February 2021 (14)
- January 2021 (5)
- December 2020 (6)
- November 2020 (12)
- October 2020 (5)
- September 2020 (5)
- August 2020 (5)
- July 2020 (14)
- June 2020 (12)
- May 2020 (6)
- April 2020 (3)
- March 2020 (4)
- February 2020 (13)
- January 2020 (3)
- December 2019 (4)
- November 2019 (7)
- October 2019 (4)
- September 2019 (12)
- August 2019 (6)
- July 2019 (5)
- June 2019 (5)
- May 2019 (8)
- April 2019 (11)
- March 2019 (8)
- February 2019 (11)
- January 2019 (8)
- December 2018 (3)
- November 2018 (4)
- October 2018 (7)
- September 2018 (10)
- August 2018 (8)
- July 2018 (9)
- June 2018 (6)
- May 2018 (4)
- March 2018 (1)
- December 2017 (1)
- November 2017 (1)
- May 2016 (1)
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.