|
By Ivan Tustanivskyi
You know the drill: a crash report lands in your queue with a pristine stack trace pointing at some innocent-looking function and absolutely no clue about what the player was actually doing. Were they mid-boss-fight? Alt-tabbing during a loading screen? Standing perfectly still in the tutorial? QA can’t repro it, the player’s bug report says “game crashed lol,” and you’re left staring at a callstack playing twenty questions with a core dump.
|
By Dan Mindru
I was at the dentist the other day, getting ready for my appointment. The waiting room was pompously decorated. Each chair seemed to be from a different, expensive Danish designer. As I realize I’m about to get charged through the nose, I get a notification from my beloved Mail app. ** ding ** Screenshot of GitHub email notification It’s a new Pull Request on GitHub. This one is different though. I have no idea where it came from!
|
By Serhii Snitsaruk
We recently released version 2.0.0 of Sentry’s Godot Engine SDK, bringing C#/.NET support and application metrics to general availability. That means you can now capture errors from your managed C# code and track custom metrics across your development and retail builds.
|
By Kyle Tryon
You’ve decided to step up your logging game and start sending more valuable, structured logs that you can query, aggregate, and use for debugging in production. Go, you! Now, uh, how do you actually write them? We’re not going to spend much time on what you should log. We’ve covered that already, a few times before. What we will be covering is how to actually write those logs, answering questions like: What makes a log structured is not just pairing messages with arbitrary JSON objects.
|
By James Crosswell
If your.NET app talks to MongoDB, you almost certainly want to be able to measure DB performance so that you can effectively debug any performance issues you might run into. For that, you need to know which database command was running, how long it took, and whether this was a one-off blip or part of a broader pattern. Ideally, you also want to pivot from that trace to related errors and replays without stitching the story together by hand.
|
By Mihir Mavalankar
Sentry’s Seer Agent lets you ask any questions about your data in Sentry, dive deep into that data, and fix issues faster. One of its particularly cool abilities is letting you ask questions directly about what you’re looking at in Sentry.
|
By Ben Coe
This is a follow-up to Sergiy’s post Errors, traces, logs, metrics: when to reach for what. Modern observability platforms, like Sentry, give developers a lot of choice. For a given problem, should you use traces, profiles, metrics, logs? If you take away one thing from this post, I hope it’s this: when in doubt, start by adding a few targeted log lines.
|
By Dan Mindru
This is a guest post by Dan Mindru, a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CronTool. It feels like with every release, we are walking a tightrope. We need to keep our app lightweight, stable, and performant, all the while depending on APIs that can shift at any moment (without warning, too!).
|
By Sergiy Dybskiy
Remember being excited (or dreading, depending on the stage of your career and the company you worked at) about writing unit tests? Or sweating all the details in your end-to-end and integration tests you were sure covered all the use cases your users would hit? These days a lot of UIs are slowly being replaced by a single input field and an agent that promises to deliver the same value a UI would, but with the elegance and pun-ness of a “Jarvis”.
|
By Milin Desai
More code is being written right now than at any point in our industry’s history. A year’s worth of software is now created every month, and most of it is no longer written by people. GitHub COO Kyle Daigle recently said, “There were 1 billion commits in 2025.
|
By Sentry
Tracing does a lot more than help you monitor performance. It's what ties errors, logs, and session replay together in Sentry, so you, and your agents actually know what happened. It's included in every Sentry plan.
|
By Sentry
Sentry brings errors, logs, replays, spans, and metrics together to find and fix the worst issues in your application.
|
By Sentry
Join us for a hands-on workshop where we go deep on structured logging: what to capture, how to structure it, and how to stay informed so your next incident has a paper trail.
|
By Sentry
Learn how to user agents to turn Slack alerts into autonomous RCA sessions, build incident memory, and help on-call engineers move from signal to fix faster. Join us for the live stream demo of Incident Response. We will break things on stream and let agents fix them. We will watch Droid run a real incident from alert to fix, and we show exactly what it read to get there.
|
By Sentry
Seer, Sentry's agent debugger, analyzes your issues and finds the root cause. Now you can pass that analysis directly to a GitHub Copilot agent which picks up the context, generates a fix, and opens a pull request. The agent session and PR both live on GitHub, with a link back in Sentry for easy access. This video walks through how the integration works.
|
By Sentry
You already have every error, trace, log, and replay in Sentry. Now let Seer, our agent debugger, do its thing: use that context to find what broke, why it broke, and how to fix it.
|
By Sentry
See what your users see. Don't try and guess what happened, watch it. Session Replay is a feature for Mobile and Web apps on Sentry to record user sessions as reproducible sessions. These are not videos. On web, a session replay contains the entire DOM reconstruction and DevTools. It's exactly like inspecting in Chrome DevTools locally on your machine, but in a real production session.
|
By Sentry
Andrea Griffiths is a Senior Developer Advocate at GitHub. She uses Sentry to monitor the Python scripts behind GitHub’s community streams, because when those pipelines fail, nobody knows until users start complaining. GitHub and Sentry built a loop that fixes that. Sentry catches the error, Seer diagnoses it, and Copilot drafts the fix. No one has to be in the middle of it. In this session, Paul Jaffre (Developer Experience at Sentry) breaks down what Seer is, then he and Andrea break a real script live and watch the loop catch it, diagnose it, and open the fix as a pull request.
|
By Sentry
We talk a lot about fixing bugs, but we never actually talked to one. Until now. Thank you, Judd, for your candor and bravery. Sentry will never be the same.
|
By Sentry
This video walks through connecting Sentry's MCP server to a Warp Agent, so instead of an agent starting from a raw error, it starts from Seer's actual root cause diagnosis: the error, the surrounding code, and recent commits. From there, the Warp Agent takes that diagnosis, implements the fix directly in the codebase, and opens a PR, all without leaving Warp.
- July 2026 (21)
- June 2026 (11)
- 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.