How we built an automated debugging workflow at Sentry
We built a system that uses Seer and Claude routines to automatically detect, fix, and route code issues — here's what we built and what we learned.
We built a system that uses Seer and Claude routines to automatically detect, fix, and route code issues — here's what we built and what we learned.
The OtlpIntegration connects your OpenTelemetry traces with Sentry error tracking, so you can click an error and see the OTel trace that caused it.
A stack trace tells you where your game died, not why. Session Replay for the Sentry Unreal Engine SDK attaches the last few seconds of gameplay to every crash report so you can watch what actually happened.
Most bugs sit in the backlog forever because fixing them costs more than the feature they compete with. With Sentry, Seer, and cloud coding agents, that math has changed.
Version 2.0.0 of Sentry's Godot Engine SDK brings C#/.NET support and application metrics to general availability.
Good logs are not just messages. They are small, queryable events with stable names, scalar attributes, and enough context to debug production systems.
Learn how to trace MongoDB queries in your .NET apps using OpenTelemetry instrumentation and Sentry's OTLP support, with full correlation to errors and replays.
Seer Agent now understands Sentry pages through structured semantic context instead of ASCII snapshots, cutting token usage by up to 85% while maintaining the same answer quality.
When in doubt, start by adding a few targeted log lines. Here are best practices for using logs to make your application easier to debug.
After 1.6 million downloads, the Usage app team shares how they use Sentry's crash monitoring, error tracking, size analysis, and user feedback to stay ahead of Apple platform changes.
Picking a model for your agent is a tradeoff between cost, quality, and speed. Here's a free-tier model that made things up, what an eval would and wouldn't have caught, and why reading the agent traces is how you actually decide.
More code is shipping faster than ever, and most of it is no longer written by people. The speed is the story everyone tells. What matters more is what happens after the code ships, where software is starting to notice it is broken, understand why, and write the fix itself.
Next.js already creates traces for your requests. With @vercel/otel and a couple environment variables, you can export them to any OTLP-compatible backend.
We trained and deployed a new issue grouping model that prevents 20% more duplicate issues, halves incorrect merges, and makes future model upgrades trivial.