Should you use Seer or just connect the MCP to your agent? A breakdown of what Seer, the Sentry agent plugin, the CLI, and coding agent handoffs each do — and when to reach for one over the other.
Etsy engineering manager Jay Henry on running a code slush instead of a freeze, keeping alert fatigue out of peak season, and pricing a crash in GMS.
Five months after launch, Seer Agent can now take action on your behalf in Sentry, and pull in infrastructure data from outside Sentry to diagnose issues faster.
The back/forward cache is one of the most impactful performance features on the web and one of the least observable, because success looks like silence. Here's how we made it measurable.
How we built zero-config Agent Tracing for Laravel AI during Agent Hackweek, from AI-generated defensive code to matching LLM calls with HTTP requests.
How our team used Sentry's own AI Conversations feature to debug our natural language search assistant.
Some numbers are too important to bury in a log or lose to sampling. A little video converter became the clearest case I've seen for tracking KPIs with Application Metrics.
The all-or-nothing sendDefaultPii boolean is going away. dataCollection replaces it with a dial for each category of data, so you can keep the headers you debug with and drop the values you would rather not store.
Session replay tools split into UX analytics tools and developer debugging tools. Here's how to tell which one you're evaluating, and the architectural questions that matter for each.
Every morning, a Claude Routine reads the previous night's Seer conversations, flags the broken ones, and files Linear tickets — before anyone's at their desk.
A full roundup of everything that shipped for Sentry Logs this summer — log pinning, overhauled exports, chart enhancements, terabyte-scale search, and a pile of usability fixes.
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.
