|
By Max Topolsky
Sentry Snapshots diffs screenshots on every commit and blocks the PR if there are any visual changes so you can confirm they’re intentional. Users don’t interact with code, they interact with something they can see and touch. Snapshots gives you a lightweight way to test it. It’s easier than ever to change code. It’s also easier than ever to trade quality for speed. Modern codebases need guardrails to ensure correctness.
|
By Neel Shah
Sentry’s SDK teams maintain and support SDKs for a vast ecosystem of languages and frameworks. See our release registry for a source of truth. We’re currently at 159 published packages across the entire ecosystem. If you use it, we probably support it. All of these SDKs are open source and have their own GitHub repositories that we maintain on a daily basis. And like any other open source project, we get tons of bug reports and issues on these.
|
By Sergiy Dybskiy
When should I reach for a log, a trace, or a metric? I hit that question constantly when I instrument code, and I watch coding agents hit it too. It sounds like it should be obvious. Errors, traces, logs, and metrics are the four kinds of telemetry most apps run on, four tools in one box, and they overlap enough that the honest answer is every developer’s favourite: it depends. You can stuff context into span attributes instead of logging it. You can count log events instead of emitting a metric.
|
By Eli Lennox
At Sentry, we’re obsessed with things not breaking. It’s kind of our whole deal. But for a while, our own marketing site was testing that obsession. Much of what you see on sentry.io (the marketing site, blog, open source microsite, etc.) were running on a fleet of legacy Gatsby sites powered by a traditional headless CMS. On paper, it worked.
|
By Lazar Nikolov
You already instrumented the backend with OpenTelemetry. Your services emit spans. Your teams know the OTel APIs. Maybe you already run a Collector. So when you start evaluating Sentry, the obvious question is: Do you need to replace your OpenTelemetry setup with the Sentry SDK? No. The practical answer is usually: keep OpenTelemetry where it already works, add the Sentry SDK where it gives you more application context, and send OpenTelemetry Protocol (OTLP) events to Sentry.
|
By Sergiy Dybskiy
Agents are getting better and better at fixing bugs. They’re even getting better at testing their work, thanks to headless browsers, sandboxes, simulators, etc. But what about the bugs that only show up once you bring in different browsers, languages, extensions, internet speeds, and all the other variables that get mixed in the second you ship to prod? Or all the bugs that only show up when you account for… well, humans being humans and doing weird stuff you didn’t expect them to do?
|
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 Sentry
Your AI agent just did something unexpected. Was it a hallucination? A bad tool call? Or did it actually handle things correctly? Sentry Conversations lets you replay the full exchange and find out.
|
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.
- June 2026 (3)
- May 2026 (19)
- 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.